public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chrisj at rtems dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/109282] Libgcc references sh and not $(SHELL) in Makefile.in Date: Sun, 26 Mar 2023 02:49:41 +0000 [thread overview] Message-ID: <bug-109282-4-gYfYcs4sVa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109282-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109282 --- Comment #2 from Chris Johns <chrisj at rtems dot org> --- (In reply to Andrew Pinski from comment #1) > move-if-change should work just fine with a normal POSIX shell ... It does. Maybe it was not found? > What is the error message with /bin/sh still there? The error message was: /bin/sh: line 1: 16562 Killed: 9 sh ../../../../gnu-mirror-gcc-cf59d86/libgcc/../move-if-change $dest ../../.././gcc/include/unwind.h This is the only place in the file `sh` is directly referenced like this. I did not look into this any further as `$(SHELL)` worked.
next prev parent reply other threads:[~2023-03-26 2:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-26 1:31 [Bug libgcc/109282] New: " chrisj at rtems dot org 2023-03-26 2:38 ` [Bug libgcc/109282] " pinskia at gcc dot gnu.org 2023-03-26 2:39 ` pinskia at gcc dot gnu.org 2023-03-26 2:49 ` chrisj at rtems dot org [this message] 2023-03-26 2:58 ` pinskia at gcc dot gnu.org 2023-03-26 3:01 ` pinskia at gcc dot gnu.org 2023-03-30 3:17 ` chrisj at rtems dot 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-109282-4-gYfYcs4sVa@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: linkBe 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).