From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001579]: libstdc++ build fails with uclibc headers
Date: Fri, 9 Nov 2007 06:07:36 -0800 [thread overview]
Message-ID: <2d94215ef0d943e0768e98384acff09f@busybox.net> (raw)
The following issue has been CLOSED
======================================================================
http://busybox.net/bugs/view.php?id=1579
======================================================================
Reported By: atle
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1579
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 11-08-2007 03:30 PST
Last Modified: 11-09-2007 06:07 PST
======================================================================
Summary: libstdc++ build fails with uclibc headers
Description:
Building gcc-3.4.6 with c++ support still fails as reported in the closed
issue http://bugs.uclibc.org/view.php?id=904.
The issue is reported in gcc PR14939,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14939
and a patch (incorporated in 4.2) is found here:
http://gcc.gnu.org/bugzilla/attachment.cgi?id=6132
The patch is tested with gcc-3.4.6 and uClibc-0.9.29 for the nios2
architecture, and works well. Could you please include this patch in
toolchain/gcc/3.4.6 ?
This issue is a show-stopper for compiling libstdc++ on the nios2 as we're
stuck with gcc 3.4.x.
======================================================================
----------------------------------------------------------------------
atle - 11-09-07 05:46
----------------------------------------------------------------------
I'll be darned... It works without the mentioned patch now (for nios2).
Must have been a configuration issue. Well, I guess this issue can be
closed.
----------------------------------------------------------------------
vanokuten - 11-09-07 06:07
----------------------------------------------------------------------
atle, I'm closing this issue - if you will be able to reproduce - just
reopen bug.
Issue History
Date Modified Username Field Change
======================================================================
11-08-07 03:30 atle New Issue
11-08-07 03:30 atle Status new => assigned
11-08-07 03:30 atle Assigned To => buildroot
11-08-07 03:31 atle Issue Monitored: atle
11-09-07 05:46 atle Note Added: 0002904
11-09-07 06:07 vanokuten Status assigned => closed
11-09-07 06:07 vanokuten Note Added: 0002905
======================================================================
next reply other threads:[~2007-11-09 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 14:07 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 10:40 [Buildroot] [buildroot 0001579]: libstdc++ build fails with uclibc headers bugs at busybox.net
2007-11-27 21:51 bugs at busybox.net
2007-11-09 13:46 bugs at busybox.net
2007-11-08 11:30 bugs at busybox.net
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=2d94215ef0d943e0768e98384acff09f@busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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