This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: autoconf AC_PREREQ ?
- From: "Ryan Arnold" <ryan dot arnold at gmail dot com>
- To: "Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>
- Cc: libc-help at sourceware dot org
- Date: Wed, 24 Sep 2008 10:28:57 -0500
- 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:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=K2Al6K18ayNu5tBbe1P93nj4KZy5Fdbmz2b4Val1kNM=; b=sa37xTpZ31ZuNeiFLCKcQB+0lcKcljz5VTJdO8sNCzYJQC0ref7hPS8AciJWRrjAQP weNaUrypdACjJakZ+vD8GMJFFscqA8NCF+h9tUuy2IIhDQ5ETYd7zRGq5/B+DOQoQsic D4cEOgsTuRntfyJqrAX57DJWeEH+fD9Tl033Y=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=boYI7oB8AbGaRwLldIszFJP6znqRrTqa1sRVTKDYmYe1wW1Po2Nwi2JhgDm+x0mu5k JV5PwA05shfIqVcOFeHqAcli8BsL1evApsTRjBst+Sy2eqRG7yYXnGVcl1f+25ifqQMI ZVjHtGwy1yDf2Sv9ovaXOc51YIOrYZyQaseOo=
- References: <200809240729.56161.yann.morin.1998@anciens.enib.fr>
On Wed, Sep 24, 2008 at 12:29 AM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> Hello All!
>
> I'm bringing this discussion on the glibc ML after it was (briefly)
> discussed (1) on the eglibc ML, and it turned out the issue is already
> present in the glibc tree.
>
> There are configure.in fragments throughout the glibc-2.8 tree. Those
> fragments get parsed with 'autoconf', called from the glibc Makefiles.
I ran into this last year. And like Carlos O'Donell indicated in his
parallel email what's described here should solve your problem.
http://sourceware.org/ml/libc-alpha/2008-02/msg00007.html
In general, we don't re-run autoconf. Generally Ulrich re-runs it and
checks the generated files into cvs when necessary. But like my email
indicates, this can expose some discrepancies when there's a mismatch
between Autoconf versions used to generate the base configure files
and new configure files that you may need to generate from your own
new configure.in fragments.
Regards,
Ryan S. Arnold