public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/54283] [4.8 regression] build tools don't run after cxx-conversion merge Date: Wed, 28 Nov 2012 19:21:00 -0000 [thread overview] Message-ID: <bug-54283-4-nrm5ZscGLR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54283-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54283 Alexandre Oliva <aoliva at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org --- Comment #7 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-11-28 19:21:10 UTC --- The general assumption on non-cross scenarios is that we're able to run a program created by CC and CXX. If this is not the case, not even configure-time execution tests involving the compilers would fail. This suggests to me that we don't have a bug or even a regression here; it just so happens that we use CXX now, and CXX has never worked “properly” on Rainer's setting. I suggest setting LD_LIBRARY_PATH so that CXX works “properly”, or using a CXX with -static-libstdc++ and whatever other options are needed to make newly-created executables run. I'm not sure this requires a documentation change.
next prev parent reply other threads:[~2012-11-28 19:21 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-16 13:45 [Bug bootstrap/54283] New: " ro at gcc dot gnu.org 2012-08-16 13:53 ` [Bug bootstrap/54283] " ro at gcc dot gnu.org 2012-08-16 13:55 ` ro at gcc dot gnu.org 2012-08-16 15:29 ` rguenth at gcc dot gnu.org 2012-09-19 14:33 ` rguenth at gcc dot gnu.org 2012-11-16 1:06 ` pinskia at gcc dot gnu.org 2012-11-16 9:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-11-17 10:20 ` ebotcazou at gcc dot gnu.org 2012-11-17 23:31 ` ebotcazou at gcc dot gnu.org 2012-11-28 19:21 ` aoliva at gcc dot gnu.org [this message] 2012-11-28 21:41 ` ebotcazou at gcc dot gnu.org 2012-12-18 10:30 ` jakub at gcc dot gnu.org 2012-12-18 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-12-18 12:10 ` jakub at gcc dot gnu.org 2012-12-18 12:13 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-12-19 11:59 ` ebotcazou at gcc dot gnu.org 2012-12-19 12:04 ` jakub at gcc dot gnu.org 2012-12-19 14:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2013-01-07 12:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2013-01-07 12:56 ` jakub at gcc dot gnu.org 2013-01-07 13:02 ` jakub at gcc dot gnu.org 2013-01-07 13:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-54283-4-nrm5ZscGLR@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).