public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/54279] New: first stage build with g++ fails with "." as the first component of $PATH Date: Thu, 16 Aug 2012 05:41:00 -0000 [thread overview] Message-ID: <bug-54279-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54279 Bug #: 54279 Summary: first stage build with g++ fails with "." as the first component of $PATH Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: gary@intrepid.com Posted here: http://gcc.gnu.org/ml/gcc-patches/2012-08/msg01032.html This build failure is a likely result of the recent change to compile GCC with the C++ compiler during the first stage. 1. I have "." on $PATH. 2. In one build of the latest GCC trunk, I specify CC=/usr/bin/gcc and CXX=/usr/bin/g++ and everything works. 3. In another build, I don't specify CC or CXX. Therefore they default to 'gcc' and 'g++'. This fails: g++: error trying to exec 'cc1plus': execvp: No such file or directory If I remove "." from $PATH then the configuration in 3 will build. The problem is that there is a g++ executable under the built gcc directory, but cc1plus and other g++ component parts haven't been built yet.
next reply other threads:[~2012-08-16 5:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-16 5:41 gary at intrepid dot com [this message] 2012-08-16 5:47 ` [Bug other/54279] [4.8 Regression] " pinskia at gcc dot gnu.org 2012-08-16 11:03 ` rguenth at gcc dot gnu.org 2012-09-19 14:31 ` rguenth at gcc dot gnu.org 2012-11-15 0:32 ` pinskia at gcc dot gnu.org 2012-11-15 2:51 ` pinskia at gcc dot gnu.org 2012-11-15 3:40 ` pinskia at gcc dot gnu.org 2012-11-15 4:32 ` pinskia at gcc dot gnu.org 2012-11-15 20:29 ` pinskia at gcc dot gnu.org 2012-11-28 22:11 ` pinskia at gcc dot gnu.org 2012-11-28 22:16 ` pinskia at gcc dot gnu.org 2013-02-10 12:28 ` karlson2k at gmail dot com 2022-01-08 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-54279-4@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).