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

[Freeciv-Dev] Re: MacOS X ./configure

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Freeciv developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: MacOS X ./configure
From: Reinier Post <rp@xxxxxxxxxx>
Date: Fri, 30 Nov 2001 21:46:24 +0100

On Fri, Nov 30, 2001 at 02:34:10PM +0200, Petrus Viljoen wrote:
> Brian Olson wrote:
> 
> > 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 http://bolson.org/
> 
> "gcc -v --help "  should list all options that your gcc supports (to
> stderr on my system).
> 
> so use
> "gcc -v --help > options.lst  2>&1"
> 
> and check if  -no-cpp-precomp is in options.lst.
> 
> 
> What I know of autoconf/configure is dangarous. Best  if you check with
> the people who developed  autoconf  (They should be able to give you the
> Best advice ).

The info files say the check should be in aclocal.m4, or if you generate
that with automake, in acinclude.m4.  acinclude.m4 already contains some
tests you can use as a model.  On my system, Freeciv's aclocal.m4
includes the whole of acinclude.m4; is this normal?

-- 
Reinier


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