From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure with 2010.08-rc1
Date: Wed, 11 Aug 2010 15:55:35 +0200 [thread overview]
Message-ID: <20100811155535.593127a3@surf> (raw)
In-Reply-To: <AANLkTi=O6T5Moy50MCccGEx=_fL5KHLJ3bv39ogGn6AK@mail.gmail.com>
On Wed, 11 Aug 2010 14:43:26 +0100
Will Newton <will.newton@gmail.com> wrote:
> -g -Os -c ctype_members.cc -fPIC -DPIC -o .libs/ctype_members.o
> ctype_members.cc: In constructor
> 'std::ctype_byname<_CharT>::ctype_byname(const char*, size_t) [with
> _CharT = char]':
> ctype_members.cc:59: error: invalid use of incomplete type 'struct
> __uclibc_locale_struct'
> /home/ldap/wnewton/src/git/buildroot/output/staging/usr/i686-unknown-linux-uclibc/sys-include/bits/uClibc_locale.h:85:
> error: forward declaration of 'struct __uclibc_locale_struct'
> ctype_members.cc:60: error: invalid use of incomplete type 'struct
> __uclibc_locale_struct'
> /home/ldap/wnewton/src/git/buildroot/output/staging/usr/i686-unknown-linux-uclibc/sys-include/bits/uClibc_locale.h:85:
> error: forward declaration of 'struct __uclibc_locale_struct'
> ctype_members.cc:61: error: invalid use of incomplete type 'struct
> __uclibc_locale_struct'
> /home/ldap/wnewton/src/git/buildroot/output/staging/usr/i686-unknown-linux-uclibc/sys-include/bits/uClibc_locale.h:85:
> error: forward declaration of 'struct __uclibc_locale_struct'
> make[5]: *** [ctype_members.lo] Error 1
> make[5]: *** Waiting for unfinished jobs....
> make[5]: Leaving directory
> `/home/ldap/wnewton/src/git/buildroot/output/toolchain/gcc-4.2.4-final/i686-unknown-linux-uclibc/libstdc++-v3/src'
>
> Time to turn off uClibc locales I think...
Ah, ah. I thought this problem was only affecting the AVR32
architecture, so we added 60f945e47a15e10f0e777f69b05492b6f7ba918d to
the tree to prevent uClibc 0.9.31 + C++ + locale from being choosen on
AVR32. But it seems that 0.9.31 + C++ + locale fails to build on any
architecture with gcc 4.2.
I've discussed the issue a few weeks ago with Berhnard on IRC, but I
didn't quite get what the solution was.
Concerning the original problem, I've started discussing with Khem on
IRC, but he didn't manage to reproduce it for some reason. One possible
solution is to somehow revert to the two-stage gcc build procedure for
gcc 4.2 and use the three-stage gcc build procedure only for gcc 4.3+.
But I'd prefer to have Khem opinion on this beforehand.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-08-11 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 12:22 [Buildroot] Build failure with 2010.08-rc1 Will Newton
2010-08-10 13:23 ` Will Newton
2010-08-10 16:23 ` Thomas Petazzoni
2010-08-10 16:28 ` Will Newton
2010-08-11 13:43 ` Will Newton
2010-08-11 13:55 ` Thomas Petazzoni [this message]
2010-08-11 15:19 ` Will Newton
2010-08-11 20:49 ` Khem Raj
2010-08-12 10:07 ` Will Newton
2010-08-12 10:02 ` Will Newton
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=20100811155535.593127a3@surf \
--to=thomas.petazzoni@free-electrons.com \
--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