On Tue, Nov 11, 2008 at 08:21:12AM -0700, Jerry James wrote: > GCL will not run successfully if compiled with -fstack-protector. It has > its own internal stack management code that interacts badly with > -fstack-protector. So I decided to try filtering that option out of the > default CFLAGS. I put this at the top of the GCL spec file: We used to do something like this for the MinGW packages, since -fstack-protector also causes a problem under Windows / MinGW cross-compilation: CFLAGS="$RPM_OPT_FLAGS -fno-stack-protector" \ ./configure [etc] (example: http://hg.et.redhat.com/misc/fedora-mingw--devel/?fd=136ab7f25dc2;file=gnutls/mingw-gnutls.spec ) I should hasten to add that we don't do that any more, because we defined our own %{_mingw32_cflags} macro so we'd have finer control. Also, if anyone can fix -fstack-protector on Windows / MinGW, please help! Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
