public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/52887] Bootstrap on AIX failure: Undefined symbol: .std::function<void (std::__regex::_PatternCursor const&, std::__regex::_Results&)>::function(std::function<void (std::__regex::_PatternCursor const&, std::__regex::_Results&)> const&) Date: Tue, 19 Jun 2012 23:21:00 -0000 [thread overview] Message-ID: <bug-52887-4-rLiQblZzVD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52887-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52887 David Edelsohn <dje at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-06-19 CC| |dje at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #13 from David Edelsohn <dje at gcc dot gnu.org> 2012-06-19 23:21:27 UTC --- I successfully bootstrap on AIX 5.3 multiple times per week with the need of the additional instantiations. This may be due to different versions of the AIX assembler. The system I am using has bos.adt.base level 5.3.7.0 installed. I also do not use many of the additional configure options. --disable-shared probably is a bad choice. The file format used on AIX is XCOFF. The file format used on most other systems is ELF. ELF provides a richer set of features for symbols and sections that GCC implicitly assumes to support C++ features. Additionally, SVR4/ELF semantics allows linkers to play a little more "fast and loose". Basically, SVR4/ELF lazy binding allows libraries to omit symbol definitions if they never are used. I suspect that the instantiations that Jonathan is adding truly are needed and should be defined for all systems, but the other systems silently ignore the error. And this probably works on my builds of AIX because I build shared libraries with an option for SVR4-like semantics that allows link-time errors during shared library creation. So the real answer probably is that the instantiations are necessary and libstdc++ really has a latent bug that is not visible on other systems.
next prev parent reply other threads:[~2012-06-19 23:21 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-06 15:38 [Bug bootstrap/52887] New: " skunk at iskunk dot org 2012-04-10 9:13 ` [Bug bootstrap/52887] " redi at gcc dot gnu.org 2012-05-10 14:39 ` skunk at iskunk dot org 2012-05-10 15:04 ` redi at gcc dot gnu.org 2012-05-10 15:52 ` skunk at iskunk dot org 2012-05-10 22:14 ` skunk at iskunk dot org 2012-05-11 17:09 ` skunk at iskunk dot org 2012-05-11 18:39 ` redi at gcc dot gnu.org 2012-05-12 5:37 ` skunk at iskunk dot org 2012-05-12 9:15 ` paolo.carlini at oracle dot com 2012-06-18 9:44 ` joerg.richter@pdv-fs.de 2012-06-18 15:26 ` redi at gcc dot gnu.org 2012-06-18 16:57 ` skunk at iskunk dot org 2012-06-19 23:21 ` dje at gcc dot gnu.org [this message] 2012-06-20 1:36 ` redi at gcc dot gnu.org 2012-06-20 4:11 ` skunk at iskunk dot org 2012-06-20 8:50 ` redi at gcc dot gnu.org 2012-06-20 13:25 ` dje at gcc dot gnu.org 2012-06-20 21:15 ` dje at gcc dot gnu.org 2012-06-21 6:58 ` joerg.richter@pdv-fs.de 2012-06-21 8:24 ` redi at gcc dot gnu.org 2012-07-25 3:19 ` skunk at iskunk dot org 2012-09-14 7:58 ` joerg.richter@pdv-fs.de 2012-09-16 2:37 ` dje at gcc dot gnu.org 2012-11-21 8:03 ` gilles.pion at gmail dot com 2012-11-26 2:50 ` dje at gcc dot gnu.org 2013-01-17 1:40 ` redi at gcc dot gnu.org 2013-01-17 1:41 ` redi at gcc dot gnu.org 2013-02-11 23:54 ` bkoz 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-52887-4-rLiQblZzVD@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).