On Wednesday October 15 2008 04:21:34 pm Valter Douglas Lisbôa Jr. wrote:
> > When GCC 4.1 released libssp, Glibc copied all of libssp in to Glibc, for
> > better performance.
>
> Statically?

In libc.so. I'm not sure what you mean by statically.

> > This happened in Glibc 2.4 or 2.5. If you're running a
> > new Glibc, libssp can not be used because it will conflict with identical
> > functions in Glibc.
> >
> > The only way I can think of using libssp is when cross compiling...
> > linking to another libc with no ssp support, and libssp.a.

This probably wouldn't work by the way, if libssp.a has symbols from Glibc.

> Let me see if I get the point. The Stack Smash protector run without the
> presence of libssp.{so,a}, is that?!?!

Yes.

robert

Attachment: pgpifVCWQIwch.pgp
Description: PGP signature

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to