On 3/13/2013 06:50, Erik de Castro Lopo wrote: > JonY wrote: > >> Dave, my toolchain automatically links libssp already, I am using >> vanilla sources. > > Are you doing a native Windows compile with MinGW or cross compiling > from Linux? >
Crossing from Cygwin, GCC built from vanilla FSF sources. >> Why not also check if -lssp is required? If the toolchain has SSP >> disabled it should not be passing. Check onces without -lssp and another >> time with -lssp if it failed. > > If we can easily force the linking of libssp then that maky work. I'm > not real keen on having the Windows DLL require this extra libssp-X.dll. > I guess that's libtool doing it. The link test that I used certainly did not require the DLL. >> Also, I don't think a trivial hello world will cause SSP code to be >> emitted, try adding some arrays in stack with a deliberate overrun >> possibility for the link test. > > Unfortunately its even more complicated than that. It can sucessfully > link and create a valid executable (with and without -lssp) which then > fails at run time because it can't find libssp-0.dll. > Libtool forces all DLL code to link to other DLLs. > This stuff is broken. I cannot see any reasonable way to make this > work across the board. The best option I can suggest is a > > ./configure --enable-stack-smash-protect > > which is disabled by default. > I am OK with this.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
