I'm trying to build Gnu binutils with behaviour unlocked by defining the macro
SYSV386_COMPAT 0 to vary the way in which it generates some FPU opcodes.
I can easily go into the header file and set the value manually, but how would I invoke the configure script in order to specify the equivalent of
#define SYSV386_COMPAT 0 on the command line? I would prefer to specify something on the command line if at all possible (just because the feature is transitive and I don't think I should be hacking the source). Having said that, I have tried to read at least some of the FM but have had no luck with inserting an
AC_DEFINE(SYSV386_COMPAT, 0) en cualquiera
preguntado el 09 de marzo de 12 a las 13:03
OK, so continued searching through other
autoconf-tagged answers took me to the second comment for este responder.
I was able to use a similar syntax to invoke
configure to get the result I was after:
./configure CPPFLAGS=-DSYSV386_COMPAT=0 --prefix=/path/to/my/deploy/dir
Thanks to William Pursell for his comment above pointing out the benefits of using
CPPFLAGS en lugar de
CFLAGS, and to anyone who was preparing to answer this question. If you have any further comments about the "best" way of solving this problem then please add to this thread for those coming to it later.
Los mejores deseos,