public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57119] libstdc++-6.dll missed in default gcc 4.8 build
Date: Tue, 30 Apr 2013 10:34:00 -0000 [thread overview]
Message-ID: <bug-57119-4-WFNehvdYte@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57119-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57119
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
--- Comment #2 from Kai Tietz <ktietz at gcc dot gnu.org> 2013-04-30 10:33:59 UTC ---
Hmm, I can't reproduce that. I just built things myself again for 4.8.1 gcc.
I am a bit curious to read that due distributions like Fedora seem to be able
to build stuff without isssues for 4.8.x gcc.
First advice would be to look into libstdc++'s config.log to see why for you
shared library isn't built. Second question is how you are actual configuring
it, and what additional patches you might use on built?
next prev parent reply other threads:[~2013-04-30 10:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 1:37 [Bug libstdc++/57119] New: " dongsheng.song at gmail dot com
2013-04-30 9:23 ` [Bug target/57119] " paolo.carlini at oracle dot com
2013-04-30 10:34 ` ktietz at gcc dot gnu.org [this message]
2013-04-30 10:42 ` dongsheng.song at gmail dot com
2013-04-30 10:44 ` dongsheng.song at gmail dot com
2013-04-30 10:46 ` dongsheng.song at gmail dot com
2013-04-30 10:47 ` dongsheng.song at gmail dot com
2013-04-30 11:00 ` ktietz at gcc dot gnu.org
2013-04-30 11:29 ` dongsheng.song at gmail dot com
2013-04-30 11:41 ` dongsheng.song at gmail dot com
2013-04-30 11:42 ` dongsheng.song at gmail dot com
2013-04-30 11:43 ` dongsheng.song at gmail dot com
2013-04-30 13:49 ` ktietz at gcc dot gnu.org
2013-04-30 14:46 ` dongsheng.song at gmail dot com
2013-12-06 0:36 ` ktietz at gcc dot gnu.org
2013-12-06 6:28 ` dongsheng.song at gmail dot com
2015-02-10 17:26 ` ktietz 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-57119-4-WFNehvdYte@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).