How to run the testsuite with non-gcc and/or extra options?

[Anthony Green]

On 3/21/2012 9:38 AM, Peter Rosin wrote:
> Hi!
>
> If I confiOn 3/21/2012 9:38 AM, Peter Rosin wrote:gure libffi as:
>
> $ mkdir foo
> $ cd foo
> $ ../configure CC=whatever
>
> And then "make", the library is built with whatever C compiler I specified.
> But if I then do "make check", the testsuite insists on using gcc, and
> it insists on using the flags specified in testsuite/libffi.call/call.exp
> and testsuite/libffi.special/special.exp.  I can't figure out how to
> make the testsuite use some other compiler or how to add more switches
> to the used compiler (MinGW gcc *needs* -posix, or something equivalent,
> as it otherwise uses a printf that thinks that long doubles are the same
> size as doubles(1)).
>
> Does the testsuite really have to be this inflexible?

I think this blog entry by Ian Taylor pretty much sums up how most 
people feel about dejagnu...
http://www.airs.com/blog/archives/499

It makes sense to share a testing harness with the GCC project, as 
libffi has benefited in so many ways from being included in the GCC 
source tree.

>
> *time passes*
>
> Ok, I can create a compiler wrapper named "xgcc" and warp options and
> invoke whatever compiler I wish.  But the question still stands, why the
> inflexibility?
>
> Or rather, what is it that am I not getting?

No.

>
> Cheers,
> Peter
>
> (1) http://sourceware.org/ml/libffi-discuss/2012/msg00117.html

I believe there's a way to add target specific flags on a per test-case 
basis to the actual test-case source code, but I don't have time to look 
it up right now.   You might find examples by rummaging through GCC 
testsuite.  I can look it up tomorrow otherwise.

Thanks,

AG