This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: [patch] libffi testsuite standalone vs. gcc
- From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- To: Andreas Tobler <andreast-list at fgznet dot ch>
- Cc: libffi-discuss at sourceware dot org, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 8 Jun 2009 21:50:50 +0200
- Subject: Re: [patch] libffi testsuite standalone vs. gcc
- References: <4A2D6839.9030109@fgznet.ch>
Hello Andreas,
* Andreas Tobler wrote on Mon, Jun 08, 2009 at 09:36:25PM CEST:
> this is a try to keep the differences between the gcc-libffi testsuite
> and the libffi-standalone minimal.
> Thoughts?
> * configure.ac: Introduce a STANDALONE variable to be able to run the
> testsuite accordingly.
Yes, unless standalone libffi routine uses a bootstrap script that sets
STANDALONE, you should default to the stand-alone version, and the
in-GCC version should key off some value passed from the toplevel
makefile.
However, I don't think you can easily postpone the decision of
stand-alone-ness until configure time for all differences so easily,
for autoconf-time differences you'd use a m4 macro not a shell variable.
Cheers,
Ralf