i686-unknown-linux-gnu-gcc: undefined reference to `__memcpy_chk'

Chrissy chrissyheb@gmx.de
Fri Feb 19 14:42:00 GMT 2010

Hi Yann, All,

thanks for your introduction to ct-ng. I tried
ct-ng i686-nptl-linux-gnu
and got a step further, but it did not compile properly. I got the error
(from build.log)

[ALL  ]    /bin/bash ../libtool --tag CXX --tag disable-shared
-B/media/f_mp3/MiniFS/toolchain/i686-nptl-linux-gnu/lib/ -isystem
/media/f_mp3/MiniFS/toolchain/i686-nptl-linux-gnu/include -isystem
-fno-implicit-templates -prefer-pic -Wall -Wextra -Wwrite-strings
-Wcast-qual  -fdiagnostics-show-location=once  -ffunction-sections
-fdata-sections  -g -Os  -c -o bad_typeid.lo
[ERROR]    Build failed in step 'Installing final compiler'
[ERROR]    Error happened in
'/usr/local/lib/ct-ng-1.6.0/scripts/functions' in function
'CT_DoExecLog' (line unknown, sorry)
[ERROR]          called from
'/usr/local/lib/ct-ng-1.6.0/scripts/build/cc/gcc.sh' at line # 350 in
function 'do_cc'
[ERROR]          called from
'/usr/local/lib/ct-ng-1.6.0/scripts/crosstool-NG.sh' at line # 562 in
function 'main'
[ERROR]    Look at '/media/f_mp3/MiniFS/toolchain/build.log' for more
info on this error.

Does someone know, what the problem is?

Am 11.02.2010 19:34, schrieb Yann E. MORIN:
> Hello Chrissy, All!
> On Wednesday 10 February 2010 09:11:40 Chrissy wrote:
>> [ALL  ]    /media/Entwicklung/MiniFS/toolchain/targets/i686-unknown-linux-gnu
>> /build/build-libc/elf/librtld.os: In function `print_statistics': 
>> [ALL  ]    rtld.c:(.text+0x272): undefined reference to `__memcpy_chk'
>> [ALL  ]    rtld.c:(.text+0x33b): undefined reference to `__memcpy_chk'
>> [ALL  ]    rtld.c:(.text+0x588): undefined reference to `__memcpy_chk'
>> [ALL  ]    /media/Entwicklung/MiniFS/toolchain/targets/i686-unknown-linux-gnu
>> /build/build-libc/elf/librtld.os: In function `_dl_make_tlsdesc_dynamic': 
>> [ALL  ]    (.text+0x148b6): undefined reference to `__memset_chk'
>> [ALL  ]    collect2: ld returned 1 exit status
>> I'm compiling on an Ubuntu 9.10 with gcc 4.4.1.
>> I attached the first and the last part of build.log, I hope that helps.
> You are using quite bleeding-edge versions of gcc. Those are known to be
> particularly hard to build, especially in the case where the build machine
> is of the same kind as the target (in your case x86).
> As a first-timer, I would suggest that you start off with the existing
> sample: i686-nptl-linux-gnu. You can recall the sample that way:
>   ct-ng i686-nptl-linux-gnu    <- configure using values from the sample
>   ct-ng show-config            <- prints current configuration
> Once your sample built OK, you can _try_ to change one version _at_a_time_
> with:
>   ct-ng menuconfig
>   ct-ng build
> If you have more than one processor (or a multi-core processor), you can
> instruct crosstool-NG to build in //:
>   ct-ng build.4     (replace 4 with the actual number of processors)
> Even on a single-core system, you may benefit a bit from running two jobs:
>   ct-ng build.2
> HTH.
> Regards,
> Yann E. MORIN.

For unsubscribe information see http://sourceware.org/lists.html#faq

More information about the crossgcc mailing list