public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "baker at usgs dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/54630] [4.8 Regression] GCC 4.8 --enable-languages=c build fails: Undefined symbols: ___cxa_guard_acquire and ___cxa_guard_release Date: Mon, 26 Nov 2012 19:44:00 -0000 [thread overview] Message-ID: <bug-54630-4-jZZC6VuIs3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54630-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54630 --- Comment #19 from Larry Baker <baker at usgs dot gov> 2012-11-26 19:44:21 UTC --- (In reply to comment #18) Ian, > You can also add linker options via the configure options --with-stage1-ldflags > and --with-boot-ldflags, q.v. So, I read what the GCC configure notes had to say about --with-boot-ldflags=flags, and it sounds like exactly what Sourceery was trying to do with --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm'. That is, the default is to statically link the C and C++ run-time libraries. --with-boot-ldflags=flags This option may be used to set linker flags to be used when linking stage 2 and later when bootstrapping GCC. If neither –with-boot-libs nor –with-host-libstdcxx is set to a value, then the default is `-static-libstdc++ -static-libgcc'. > Although it is not documented specifically for GCC, you can also set LDFLAGS > when running make, as you can for all GNU programs. I might have already tried this and it fails. (I can't remember exactly.) Take a look at my Comment 6 from 2012-09-21 20:34:41. You'll see that the GCC build machinery overrides CFLAGS and LDFLAGS with CFLAGS_FOR_BUILD and LDFLAGS_FOR_BUILD, respectively. I think your first suggestion is definitely the best solution. The next time I work on this, I'll check the results of the link of the cross gcc to see if the default stage 2 build really does eliminate the dependencies on the shared C and C++ run-time libraries. Thanks.
prev parent reply other threads:[~2012-11-26 19:44 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-19 21:15 [Bug libstdc++/54630] New: " baker at usgs dot gov 2012-09-20 11:37 ` [Bug middle-end/54630] [4.8 Regression] " rguenth at gcc dot gnu.org 2012-09-20 20:28 ` baker at usgs dot gov 2012-09-20 20:30 ` baker at usgs dot gov 2012-09-21 18:58 ` baker at usgs dot gov 2012-09-21 19:17 ` baker at usgs dot gov 2012-09-21 20:35 ` baker at usgs dot gov 2012-09-22 1:14 ` baker at usgs dot gov 2012-09-22 1:45 ` baker at usgs dot gov 2012-09-25 1:53 ` baker at usgs dot gov 2012-11-19 3:02 ` jason at gcc dot gnu.org 2012-11-19 13:44 ` jakub at gcc dot gnu.org 2012-11-20 9:24 ` jakub at gcc dot gnu.org 2012-11-20 19:58 ` baker at usgs dot gov 2012-11-20 20:20 ` jakub at gcc dot gnu.org 2012-11-20 22:25 ` baker at usgs dot gov 2012-11-21 11:20 ` redi at gcc dot gnu.org 2012-11-21 21:38 ` baker at usgs dot gov 2012-11-22 0:51 ` ian at airs dot com 2012-11-26 19:44 ` baker at usgs dot gov [this message]
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-54630-4-jZZC6VuIs3@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).