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: Sat, 22 Sep 2012 01:14:00 -0000	[thread overview]
Message-ID: <bug-54630-4-sNJMxYHPmI@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 #7 from Larry Baker <baker at usgs dot gov> 2012-09-22 01:13:54 UTC ---
I'm kind of stumped at the moment to find an alternative method to pass down
linker flags without using --with-host-libstdcxx.  I tried setting

CFLAGS_FOR_BUILD="-x c -x none" \
CXXFLAGS_FOR_BUILD="-x c++ -x none" \
LDFLAGS_FOR_BUILD="-x none" \

in the configure step.  I also hacked Makefile.in to pass CXXFLAGS_FOR_BUILD in
BASE_FLAGS_TO_PASS.

The CFLAGS_FOR_BUILD="-x c -x none" show up in the gcc compile commands (the
"make gcc" screen output), but I'm not sure it is used in every gcc command. 
The CXXFLAGS_FOR_BUILD="-x c++ -x none" and LDFLAGS_FOR_BUILD="-x none" never
show up.

I don't really care that much about static linking myself.  But, I can
understand why a vendor or package developer might want to have the capability.


  parent reply	other threads:[~2012-09-22  1:14 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 [this message]
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

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-sNJMxYHPmI@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).