[Clfs-support] Having issues building GLIBC 32bit

[William Harrington]

On May 10, 2014, at 2:42 AM, Gary Greene wrote:

> /home/builder/sources/glibc-build-32/resolv/ 
> libresolv_pic.a(ns_print.os): In function `__GI_ns_sprintrrf':
> ns_print.c:(.text+0x48f): undefined reference to `__stack_chk_guard'
> ns_print.c:(.text+0x5b8): undefined reference to `__stack_chk_guard'
> /home/builder/sources/glibc-build-32/resolv/ 
> libresolv_pic.a(gethnamaddr.os): In function `getanswer':
> gethnamaddr.c:(.text+0x766): undefined reference to  
> `__stack_chk_guard'
> gethnamaddr.c:(.text+0x7a5): undefined reference to  
> `__stack_chk_guard'
> /home/builder/sources/glibc-build-32/resolv/ 
> libresolv_pic.a(gethnamaddr.os): In function  
> `__GI_res_gethostbyname2':
> gethnamaddr.c:(.text+0x109c): undefined reference to  
> `__stack_chk_guard'
> /home/builder/sources/glibc-build-32/resolv/ 
> libresolv_pic.a(gethnamaddr.os):gethnamaddr.c:(.text+0x127e): more  
> undefined references to `__stack_chk_guard' follow

echo "libc_cv_ssp=no" > config.cache

Did you do that prior to running configure as stated here:
http://cross-lfs.org/view/git/x86_64/cross-tools/glibc.html

Gcc static is built before this step with  --disable-libssp
http://cross-lfs.org/view/git/x86_64/cross-tools/gcc-static.html
I notice you are using x86_64-altimatos-linux-gnu-gcc  instead of  
x86_64-cross-linux-gnu-gcc at this step which means you changed your  
vendor in the target triplet.
You should change your vendor when you build the final system if you  
want altimatos as your vendor in the target triplet. Even though  
changing the vendor can fool autotools into thinking a cross compiler  
is being used or built, use cross as in the book to minimize some  
issues, if the issue isn't from disabling ssp during gcc final static  
or during eglibc configure.

Sincerely,
William Harrington