public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "skunk at iskunk dot 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: Mon, 18 Jun 2012 16:57:00 -0000 [thread overview]
Message-ID: <bug-52887-4-FOEaHOTtxU@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
--- Comment #12 from Daniel Richard G. <skunk at iskunk dot org> 2012-06-18 16:56:42 UTC ---
(In reply to comment #11)
> We know the instantiations that are needed, but I don't want to define them for
> all platforms if they're not needed elsewhere. I also have no way of testing on
> AIX, so someone needs to run the teststuite with the changes.
I can do the testing, but is this really the solution? Why would AIX (and not
even all versions of AIX) need these instantiations, how is it doing things
differently from other systems?
This is fine as a workaround, but I'm presuming the real fix is to get GCC on
AIX working again the same way as it does elsewhere.
next prev parent reply other threads:[~2012-06-18 16:57 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 [this message]
2012-06-19 23:21 ` dje at gcc dot gnu.org
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-FOEaHOTtxU@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).