Rob,
On 15/11/2017 17:10, Rob Arthan wrote:
- On Mac OS (and presumably any system with clang as the C compiler), the
configure script gives a warning. (I just let this go by and nothing seems to have gone wrong.)
checking for C compiler vendor... clang
- WARNING: Don't know the best CFLAGS for this system *
- Use ./configure CFLAGS=... to specify your own flags *
- (otherwise, a default of CFLAGS=-O3 will be used) *
I have seen this myself when building, remotely, on Mac OS X. I don't know if this is something that should be fixed or not.
- The configure script doesn't complain about unrecognised options beginning
with --enable. E.g,
configure --enable-garbage
just carries on. This fooled me when I managed to misspell --enable-intinf-as-int. If this is forced upon you by autoconfig, then so be it.
I did a search and came up with this: https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Option-... . Poly/ML's autoconf script uses AC_CONFIG_SUBDIRS to build libffi so that will disable all option checking. There doesn't seem to be any way to override this and turn it on within the script but --enable-option-checking does seem to work. However ./configure --enable-option-cheking doesn't produce any warning at all so it doesn't help if that is misspelled.
Regards, David