[patch] cygport-0.2.7 autoconf-2.61/automake-1.10 support
Charles Wilson
cygwin@cwilson.fastmail.fm
Sat Jan 6 02:19:00 GMT 2007
Two minor changes missed in 0.2.7's ac2.61 support:
(1) prefer --datarootdir for ac2.60 *and above*, not just ac2.60
(2) automake-1.10's aclocal inserts more stringent error checking
for autoconf version mismatch into aclocal.m4. This error
checking cause <current> autoreconf to complain if it is newer
than the autoconf used originally. See aclocal snippet below:
From aclocal-1.10:
--------------------------
if ($ac_version)
{
# Do not use "$output_file" here for the same reason we do not
# use it in the header below. autom4te will output the name of
# the file in the diagnostic anyway.
$output = "m4_if(m4_PACKAGE_VERSION, [$ac_version],,
[m4_fatal([this file was generated for autoconf $ac_version.
You have another version of autoconf. If you want to use that,
you should regenerate the build system entirely.], [63])])
--------------------------
I interpret "regenerate the build system entirely" to mean "remove all
autotool generated files before running autoreconf".
2007-01-05 Charles Wilson <...>
* bin/cygport.in: use --datarootdir in preference
to --datadir/--infodir/--mandir when using
autoconf-2.60 and later.
* autogen.sh: Ensure that autoconf will not complain
when it is newer than the one previously used (needed
because automake-1.10's aclocal now inserts more stringent
checking into aclocal.m4)
--
Chuck
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygport-ac2.61.patch
URL: <http://cygwin.com/pipermail/cygwin/attachments/20070106/88dbef86/attachment.ksh>
-------------- next part --------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list