[Clfs-support] Having issues building GLIBC 32bit

[Gary Greene]

On 10 May 2014, at 05:16am, William Harrington <kb0iic at berzerkula.org> wrote:
> 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

I did add the libc_cv_ssp=no in config.cache, as required, GCC static is configured as stated in the book.

As far as the tuple is concerned, yes, I did change it from the one in the CLFS book, as I’m using CLFS to allow me to build a clean build root for AltimatOS. My environment in the builder user (my equivalent of the clfs user) follows:

builder:/home/builder$ env
CLFS_TARGET32=i686-altimatos-linux-gnu
CLFS_HOST=x86_64-altimatos-linux-gnu
TERM=xterm
CLFS_TARGET=x86_64-altimatos-linux-gnu
LC_ALL=POSIX
BUILD64=-m64
CLFS=/AltimatOS
BUILD32=-m32
PATH=/cross-tools/bin:/cross-tools/sbin:/tools/bin:/tools/sbin:/System/bin:/System/sbin:/bin:/usr/bin
PWD=/home/builder
PS1=\u:\w\$ 
HOME=/Users/builder
_=/usr/bin/env

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 535 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.clfs.org/pipermail/clfs-support-clfs.org/attachments/20140510/3853fef8/attachment-0001.sig>