This is the mail archive of the
libffi-discuss@sources.redhat.com
mailing list for the libffi project.
Re: libffi on OpenBSD x86
- From: Anthony Green <green at redhat dot com>
- To: Thomas Heller <theller at python dot net>
- Cc: libffi-discuss at sources dot redhat dot com, gcc at gcc dot gnu dot org
- Date: Wed, 20 Oct 2004 06:38:09 -0700
- Subject: Re: libffi on OpenBSD x86
- Organization: Red Hat, Inc.
- References: <mzyhpmsg.fsf@python.net>
On Wed, 2004-10-20 at 06:00, Thomas Heller wrote:
> but it seems the stack smashing protection that OpenBSD uses prevents
> ffi_call from working correctly.
> I found the -fno-stack-protector command line option for gcc, and
> specifying this did the trick.
>
> Now I'm not sure if there is a pragma which allows to disable the stack
> protector from within the C source file, or should it be added to
> libffi/configure somehow, or is there a way to pass this switch when
> running libffi/configure?
IIRC, this flag comes from a set of third-party GCC patches. It would
certainly be easiest for the maintainer of those patches to cover the
libffi directory as well.
Alternatively, you can try setting CFLAGS_FOR_TARGET at the top-level
when you make libffi.
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.