This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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?
*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?
Cheers, Peter
(1) http://sourceware.org/ml/libffi-discuss/2012/msg00117.html
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |