Andrew Elian wrote:
> On Mon, Jul 25, 2011 at 10:19:04PM -0400, Bill Cunningham wrote:
>> I received this error message when my compilation finally broke.
>> I was doing well for a long time.
>>
>>
>> /mnt/lfs/g/nscd/nscd.o: In function `nscd_open_socket':
>> /mnt/lfs/glibc-2.13/nscd/nscd.c:442: undefined reference to
>> `__stack_chk_guard'
>>
>> Bill
>
> I ran into this odd error myself some time ago when I (just for fun)
> built LFS 6.8 using a much older LFS.
>
>> From http://lkml.indiana.edu/hypermail/linux/kernel/0902.1/01077.html
> "It seems that even with the same gcc versions, gcc built against
> libc w/o TLS support generates __stack_chk_guard, so if you mix the
> two flavors, the has-stack-protector check can be compiled on
> machines w/TLS while some other files end up being built on
> machines w/o TLS support thus circumventing the support check."
>
> I think there are two options: adding libc_cv_ssp='no' to configparms
> or
> adding -lssp for the linker. Having gone with option two I found I
> also
> needed to then supply libssp (from /tools) on the host system. Both
> of
> those seem to be hacks.
Now does this have anything with not building libssp back either
when 4.5.2 was being built? I built it with gcc-4.6.0 too if that means
anything. Remember libssp was disabled earlier. Was it built? If not how can
you link statically to it?
> It might be better to rebuild gcc (in Chapter 5) with
> -fno-stack-protection, however, I've not tried that myself.
>
> Best of luck,
> ae
>
> --
> My Blog: http://elian001.wordpress.com
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
