[Buildroot] problem generating c++ compiler for target arch

[Buildroot] problem generating c++ compiler for target arch

[lists at primefarm.co.uk]

Hi all,

I'm using buildroot to generate cross compilers for the arm 920t running
linux. Currently I have a working C compiler, but I really want c++
working too.

I get the following error when building (with latest svn release) with
fairly minimal options (I have tried to configure it so that it only
builds the compilers and related libs etc where possible).

In file included from
/home/david/buildroot/toolchain_build_arm/gcc-3.4.2/libstdc++-v3/src/ext-inst.cc:34:
/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3/include/ext/rope:934:
error: expected `;' before "const"
/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3/include/ext/rope:935:
error: expected `;' before "_Rope_iterator_base"
/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3/include/ext/rope:2011:36:
macro "index" requires 2 arguments, but only 1 given
...
[last message repeated lots for differnt lines]
...
/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3/include/ext/ropeimpl.h:1503:66:
macro "index" requires 2 arguments, but only 1 given
make[4]: *** [ext-inst.lo] Error 1
make[4]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/arm-linux-uclibc/libstdc++-v3'
make[1]: *** [all-target-libstdc++-v3] Error 2
make[1]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final'
make: ***
[/home/david/buildroot/toolchain_build_arm/gcc-3.4.2-final/.compiled]
Error 2


If needed I can supply a copy of my .config. I'm aware that buildroot is
massively complex and that is possibly why I'm having such troubles. If
anyone knows a better way to get a working c/c++ compiler for my CPU, and
working with uclibc and uclibc++ I'd be interested.


Cheers,

David

[Buildroot] problem generating c++ compiler for target arch

[Bernhard Fischer]

On Wed, Nov 22, 2006 at 06:06:31PM -0000, lists at primefarm.co.uk wrote:
>Hi all,
>
>I'm using buildroot to generate cross compilers for the arm 920t running
>linux. Currently I have a working C compiler, but I really want c++
>working too.
>
>I get the following error when building (with latest svn release) with
>fairly minimal options (I have tried to configure it so that it only
>builds the compilers and related libs etc where possible).

I take it that 3.4.6 works, yes?
At least the index thing is fixed in 3.4.6 and later and i believe also
the rope.

[Buildroot] problem generating c++ compiler for target arch

[lists at primefarm.co.uk]

On Wed, November 22, 2006 6:52 pm, Bernhard Fischer wrote:
> On Wed, Nov 22, 2006 at 06:06:31PM -0000, lists at primefarm.co.uk wrote:
>
>> Hi all,
>>
>>
>> I'm using buildroot to generate cross compilers for the arm 920t
>> running linux. Currently I have a working C compiler, but I really want
>> c++ working too.
>>
>> I get the following error when building (with latest svn release) with
>> fairly minimal options (I have tried to configure it so that it only
>> builds the compilers and related libs etc where possible).
>
> I take it that 3.4.6 works, yes?
> At least the index thing is fixed in 3.4.6 and later and i believe also
> the rope.
>

OK, I tried again with 3.4.6, those errors do indeed go away. I now have a
differnt set of problems (hooray!).

The error seems to center around fakeroot, although I'm no expert at
reading these error dumps.

Here is the whole lot:

CONFIG_FILES= CONFIG_HEADERS= /bin/sh ./config.status
config.status: executing depfiles commands
config.status: executing libtool commands
/bin/sh ./libtool --tag=CC --mode=link gcc  -g -O2   -o faked  faked.o
libcommunicate.la -ldl
libtool: link: gcc -g -O2 -o faked faked.o  ./.libs/libcommunicate.a -ldl
/usr/lib/libc_nonshared.a(elf-init.oS)(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0):
In function `__i686.get_pc_thunk.bx':
: multiple definition of `__i686.get_pc_thunk.bx'
./.libs/libcommunicate.a(communicate.o)(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0):/home/david/buildroot/toolchain_build_arm/fakeroot-1.5.8/communicate.c:72:
first defined here
collect2: ld returned 1 exit status
make[3]: *** [faked] Error 1
make[3]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/fakeroot-1.5.8'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/fakeroot-1.5.8'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/david/buildroot/toolchain_build_arm/fakeroot-1.5.8'
make: *** [/home/david/buildroot/toolchain_build_arm/fakeroot-1.5.8/faked]
Error 2



Any ideas?


David

[Buildroot] problem generating c++ compiler for target arch

[Bernhard Fischer]

On Wed, Nov 22, 2006 at 07:44:38PM -0000, lists at primefarm.co.uk wrote:
>On Wed, November 22, 2006 6:52 pm, Bernhard Fischer wrote:

>OK, I tried again with 3.4.6, those errors do indeed go away. I now have a
>differnt set of problems (hooray!).
>
>The error seems to center around fakeroot, although I'm no expert at
>reading these error dumps.
>
>Here is the whole lot:
>
>CONFIG_FILES= CONFIG_HEADERS= /bin/sh ./config.status
>config.status: executing depfiles commands
>config.status: executing libtool commands
>/bin/sh ./libtool --tag=CC --mode=link gcc  -g -O2   -o faked  faked.o
>libcommunicate.la -ldl
>libtool: link: gcc -g -O2 -o faked faked.o  ./.libs/libcommunicate.a -ldl
>/usr/lib/libc_nonshared.a(elf-init.oS)(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0):
>In function `__i686.get_pc_thunk.bx':
>: multiple definition of `__i686.get_pc_thunk.bx'

>
>Any ideas?

Not sure, but it sounds like your host's toolchain is too old.
binutils-2.16.1 work for me..

[Buildroot] problem generating c++ compiler for target arch

[lists at primefarm.co.uk]

On Wed, November 22, 2006 8:02 pm, Bernhard Fischer wrote:
> On Wed, Nov 22, 2006 at 07:44:38PM -0000, lists at primefarm.co.uk wrote:
>
>> On Wed, November 22, 2006 6:52 pm, Bernhard Fischer wrote:
>>
>
>> OK, I tried again with 3.4.6, those errors do indeed go away. I now
>> have a differnt set of problems (hooray!).
>>
>> The error seems to center around fakeroot, although I'm no expert at
>> reading these error dumps.
>>
>> Here is the whole lot:
>>
>>
>> CONFIG_FILES= CONFIG_HEADERS= /bin/sh ./config.status
>> config.status: executing depfiles commands
>> config.status: executing libtool commands
>> /bin/sh ./libtool --tag=CC --mode=link gcc  -g -O2   -o faked  faked.o
>> libcommunicate.la -ldl libtool: link: gcc -g -O2 -o faked faked.o
>> ./.libs/libcommunicate.a -ldl
>> /usr/lib/libc_nonshared.a(elf-init.oS)(.gnu.linkonce.t.__i686.get_pc_thu
>> nk.bx+0x0):
>> In function `__i686.get_pc_thunk.bx':
>> : multiple definition of `__i686.get_pc_thunk.bx'
>>
>
>>
>> Any ideas?
>>
>
> Not sure, but it sounds like your host's toolchain is too old.
> binutils-2.16.1 work for me..
>


I'm running it on 2.16.1 already. The box im running it on is debian sarge
- which could explain some random things being far too old.

What newer versions of binutils do you reccomend?

[Buildroot] problem generating c++ compiler for target arch

[Bernhard Fischer]

On Wed, Nov 22, 2006 at 08:09:05PM -0000, lists at primefarm.co.uk wrote:
>On Wed, November 22, 2006 8:02 pm, Bernhard Fischer wrote:
>> On Wed, Nov 22, 2006 at 07:44:38PM -0000, lists at primefarm.co.uk wrote:
>>
>>> On Wed, November 22, 2006 6:52 pm, Bernhard Fischer wrote:
>>>
>>
>>> OK, I tried again with 3.4.6, those errors do indeed go away. I now
>>> have a differnt set of problems (hooray!).
>>>
>>> The error seems to center around fakeroot, although I'm no expert at
>>> reading these error dumps.
>>>
>>> Here is the whole lot:
>>>
>>>
>>> CONFIG_FILES= CONFIG_HEADERS= /bin/sh ./config.status
>>> config.status: executing depfiles commands
>>> config.status: executing libtool commands
>>> /bin/sh ./libtool --tag=CC --mode=link gcc  -g -O2   -o faked  faked.o
>>> libcommunicate.la -ldl libtool: link: gcc -g -O2 -o faked faked.o
>>> ./.libs/libcommunicate.a -ldl
>>> /usr/lib/libc_nonshared.a(elf-init.oS)(.gnu.linkonce.t.__i686.get_pc_thu
>>> nk.bx+0x0):
>>> In function `__i686.get_pc_thunk.bx':
>>> : multiple definition of `__i686.get_pc_thunk.bx'
>>>
>>
>>>
>>> Any ideas?
>>>
>>
>> Not sure, but it sounds like your host's toolchain is too old.
>> binutils-2.16.1 work for me..
>>
>
>
>I'm running it on 2.16.1 already. The box im running it on is debian sarge
>- which could explain some random things being far too old.
>
>What newer versions of binutils do you reccomend?

Perhaps try a more recent gcc for your host.
If sarge's gcc is older than 3.4.6, then i'd bootstrap the 3.4.6 you
already downloaded. If this fails to work properly, then i guess4.{1,2}
should work fine.

HTH,

[Buildroot] problem generating c++ compiler for target arch

[lists at primefarm.co.uk]

OK,

I managed to get buildroot to complete the build at last. Sadly, the c++
compiler is b0rked.

Looks like it's missing all sorts of libraries and things. Here is some
sample output trying to compile a very simple program (C++ hello world):


david at tulip:~/buildroot/build_arm/staging_dir/bin$ ./arm-linux-gcc foo.cpp
/tmp/ccNH0d2c.o: In function `std::__verify_grouping(char const*, unsigned
int, std::basic_string<char, std::char_traits<char>, std::allocator<char>
> const&)':
foo.cpp:(.text+0x20): undefined reference to `std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::size() const'
foo.cpp:(.text+0x98): undefined reference to `std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::operator[](unsigned int)
const'
foo.cpp:(.text+0x100): undefined reference to `std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::operator[](unsigned int)
const'
foo.cpp:(.text+0x144): undefined reference to `std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::operator[](unsigned int)
const'
/tmp/ccNH0d2c.o: In function `main':
foo.cpp:(.text+0x1ac): undefined reference to `std::basic_ostream<char,
std::char_traits<char> >& std::operator<< <std::char_traits<char>
>(std::basic_ostream<char, std::char_traits<char> >&, char const*)'
foo.cpp:(.text+0x1bc): undefined reference to `std::cout'
/tmp/ccNH0d2c.o: In function
`__static_initialization_and_destruction_0(int, int)':
foo.cpp:(.text+0x200): undefined reference to `std::ios_base::Init::Init()'
foo.cpp:(.text+0x228): undefined reference to `std::ios_base::Init::~Init()'
collect2: ld returned 1 exit status
david at tulip:~/buildroot/build_arm/staging_dir/bin$ cat foo.cpp
cat: foo.cpp: No such file or directory


All sorts of things missing there - have I inadvertantly broken lots of
buildroot?

David

[Buildroot] problem generating c++ compiler for target arch

[MikeW]

<lists@...> writes:

>
> OK,
>
> I managed to get buildroot to complete the build at last. Sadly, the c++
> compiler is b0rked.
>
> Looks like it's missing all sorts of libraries and things. Here is some
> sample output trying to compile a very simple program (C++ hello world):
>
> david <at> tulip:~/buildroot/build_arm/staging_dir/bin$ ./arm-linux-gcc foo.cpp
> /tmp/ccNH0d2c.o: In function `std::__verify_grouping(char const*, unsigned
> int, std::basic_string<char, std::char_traits<char>, std::allocator<char>
> > const&)':
> foo.cpp:(.text+0x20): undefined reference to `std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >::size() const'
> foo.cpp:(.text+0x98): undefined reference to `std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >::operator[](unsigned int)
> const'
...
> 
> All sorts of things missing there - have I inadvertantly broken lots of
> buildroot?
>
> David
>

Did you specify libstdc++ in your menuconfig ?
                                                                               
MikeW






xxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxx
xxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxx

[Buildroot] problem generating c++ compiler for target arch

[David Prime]

On Wed, November 29, 2006 5:45 pm, MikeW wrote:
> <lists@...> writes:
>
>
>>
>> OK,
>>
>>
>> I managed to get buildroot to complete the build at last. Sadly, the
>> c++ compiler is b0rked.
>>
>> Looks like it's missing all sorts of libraries and things. Here is some
>>  sample output trying to compile a very simple program (C++ hello
>> world):
>>
>>
>> david <at> tulip:~/buildroot/build_arm/staging_dir/bin$ ./arm-linux-gcc
>> foo.cpp /tmp/ccNH0d2c.o: In function `std::__verify_grouping(char
>> const*, unsigned int, std::basic_string<char, std::char_traits<char>,
>> std::allocator<char>
>>
>>> const&)':
>>>
>> foo.cpp:(.text+0x20): undefined reference to `std::basic_string<char,
>> std::char_traits<char>, std::allocator<char> >::size() const'
>> foo.cpp:(.text+0x98): undefined reference to `std::basic_string<char,
>> std::char_traits<char>, std::allocator<char> >::operator[](unsigned int)
>>  const'
> ...
>
>>
>> All sorts of things missing there - have I inadvertantly broken lots of
>>  buildroot?
>>
>> David
>>
>>
>
> Did you specify libstdc++ in your menuconfig ?


Yes of course, but it's failing mysteriously. It seems to get built but I
dunno where it breaks down after that, I've not much experience with this
compiler bootstrapping stuff.