This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: autoconf AC_PREREQ ?
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>
- Cc: libc-help at sourceware dot org
- Date: Tue, 30 Sep 2008 17:20:49 -0400
- Subject: Re: autoconf AC_PREREQ ?
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=tnf2jQv1I5UJtpxhxk721WWzQAKECqFE7vGlSLuW/bw=; b=AVi2l9qzYIf4aoBYDLzK6v4Sqfpp/OLyAvEa6yGmjd/rvo19AHZoZY1SrYfmM8c4l2 QiurnkW+H9jigbrfuU/PaI+wft4M/UGcyg4f2j81Z3by7+dKMXq6NvUUkrQiJlheF5Ba 8uRcSel7veWnN34DXN9XeFEhQhMXFTJLS7D4c=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=WzQ8efN2wtaRffjmRTbyYGwExLsDn1HtUWs+P+GSeR5ZdiL1t3BsXkYtP9EZ02vvOt Flbujtu9UYIQDIoinNYOq1ScMccagfewC4TySjImZ2EUy6w2fY1jrcFwENu2U6UDDo5W qbgGPfFnZgihdiCwyIlGGDdpv3oEbal7XPjWE=
- References: <200809240729.56161.yann.morin.1998@anciens.enib.fr> <200809241937.56133.yann.morin.1998@anciens.enib.fr> <119aab440809301322k772faa3al229097af417df4b5@mail.gmail.com> <200809302247.35377.yann.morin.1998@anciens.enib.fr>
On Tue, Sep 30, 2008 at 4:47 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
>> The glibc configure.in files are only fragments, and do not use
>> AC_INIT or AC_PREREQ.
>
> Maybe they are fragments, but autoconf *is* run against them, a-la (line
> manually split):
> autoconf sysdeps/unix/sysv/linux/powerpc/configure.in > \
> sysdeps/unix/sysv/linux/powerpc/configure
>
> So, when run, autoconf sees neither AC_PREREQ nor AC_INIT. Or am I missing
> something?
No, that is correct. Each fragment is *processed* by autoconf, but
the fragments are *run* by the top-level configure.in script which is
the only script that needs the AC_PREREQ.
See the configure.in code which prints the message "running the
configure fragment for".
Cheers,
Carlos.