Complete.Org: Mailing Lists: Archives: freeciv-dev: November 2001:
[Freeciv-Dev] MacOS X ./configure

[Freeciv-Dev] MacOS X ./configure

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] MacOS X ./configure
From: Brian Olson <locke@xxxxxxx>
Date: Thu, 29 Nov 2001 23:52:37 -0800

Any autoconf guru's out there? There was some discussion a while ago about the Right Way to get autoconf to detect Apple's peculiar compiler and change $CC to be $CC -no-cpp-precomp. "-no-cpp-precomp" is an adaptation that I believe only exists in the apple (g)cc because it's there to fix Apple/NeXT's optimization that broke compatibility with mainline gcc. Unfortunately, gcc just notes unknown flags with a minor warning to stderr and doen't do anything as drastic and scriptably useful as exiting with error.

But, any thoughts on the difficulty of getting autoconf/configure to detect a presence/absence of stderr output on a command like
$CC -no-cpp-precomp -E - < /dev/null

macosx% cc -no-cpp-precomp -E - < /dev/null
# 1 ""
freebsd% gcc -no-cpp-precomp -E - < /dev/null
gcc: unrecognized option `-no-cpp-precomp'
# 1 ""

[insert clever signoff here]
Brian Olson

[Prev in Thread] Current Thread [Next in Thread]