autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: undefined macro: AF_INET ?


From: Bernard Dautrevaux
Subject: RE: undefined macro: AF_INET ?
Date: Thu, 18 Jan 2001 16:26:38 +0100

> -----Original Message-----
> From: Akim Demaille [mailto:address@hidden
> Sent: Thursday, January 18, 2001 3:32 PM
> To: Lars J. Aas
> Cc: Russ Allbery; Autoconf List
> Subject: Re: undefined macro: AF_INET ?
> 
> 
> >>>>> "Lars" == Lars J Aas <address@hidden> writes:
> 
> Lars> I believe `AR_FLAGS' has been mentioned in the same context a
> Lars> couple of times.  `AS_FLAGS' for the assembler?
> 
> Right.
> 
> Up to now AF_INET, A[RS]_FLAGS.
> 

bash$ find . -name '*.h' | xargs -n64 grep '\<A[A-Z]_' ) | sed -n -e
's/^.*\(\<A[A-Z]_[A-Za-z0-9]*\).*$/\1/p' | sort | uniq 

You'll get about 95 such things, not counting the various make macros like
above... All these are from A[BCFIMPRTUV]; of those we only use for now in
autotools A[CMU]. This reduces the list of exceptions to 6 (AC_C, AC_DENY,
AC_PERMIT, AM_STR, AU_NULL, AU_PVTYPE). 

I know we also use AT_, but that's for autotest, so I'm not sure its useful
for autoconf to check these are all expanded: if they aren't, the test will
fail anyway :-)

So I again have to say that it's to be a bit too picky to reject all
A[AZ]_xxxx identifiers as unexpanded autotool macros.

Regards,

        Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:    +33 (0) 1 47 68 80 80
Fax:    +33 (0) 1 47 88 97 85
e-mail: address@hidden
                address@hidden
-------------------------------------------- 



reply via email to

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