public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106429] Building GCC is Inhibited on old Linux Distributions due to the use of "#!/bin/bash"
Date: Sat, 30 Jul 2022 01:51:22 +0000	[thread overview]
Message-ID: <bug-106429-4-qCbQmm0pTi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106429-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Vahi from comment #5)
> Created attachment 53385 [details]

This is a failure while "make clean".

And your patch does not even touch anything related to libgcc and "make clean".

So this is a different issue from what you reported.

  parent reply	other threads:[~2022-07-30  1:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 22:48 [Bug other/106429] New: " martin.vahi at softf1 dot com
2022-07-24 23:04 ` [Bug other/106429] " pinskia at gcc dot gnu.org
2022-07-24 23:07 ` pinskia at gcc dot gnu.org
2022-07-24 23:10 ` pinskia at gcc dot gnu.org
2022-07-25  9:35 ` redi at gcc dot gnu.org
2022-07-30  1:38 ` martin.vahi at softf1 dot com
2022-07-30  1:45 ` martin.vahi at softf1 dot com
2022-07-30  1:51 ` pinskia at gcc dot gnu.org [this message]
2022-07-30  2:27 ` martin.vahi at softf1 dot com
2022-07-30  5:25 ` [Bug other/106429] make clean in libgcc fails pinskia at gcc dot gnu.org
2022-07-30  5:27 ` pinskia at gcc dot gnu.org
2022-07-31  9:45 ` martin.vahi at softf1 dot com
2022-07-31  9:49 ` martin.vahi at softf1 dot com
2022-07-31 10:33 ` redi at gcc dot gnu.org
2022-07-31 10:36 ` redi at gcc dot gnu.org
2022-07-31 14:32 ` egallager at gcc dot gnu.org
2023-06-05  4:08 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106429-4-qCbQmm0pTi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).