Summary: | obsolete.test fails for automake 1.8.5-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Brant Gurganus <brant> |
Component: | [OLD] Development | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Brant Gurganus
2004-10-25 23:08:24 UTC
Upstream said that it looks like the autoconf wrapper is calling the wrong autoconf version. Here are the replies they gave: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brant Gurganus <gurganbl@rose-hulman.edu> writes: >> Alexandre Duret-Lutz wrote: >> > >>>>>> >>>>"Brant" == Brant Gurganus <gurganbl@rose-hulman.edu> writes: >>>>>> >>>> >>>>>> >>>> >> >>> > >>> > Brant> The obsolete.test test case failed for version 1.8.5-r1 on Gentoo. >>> > Brant> The results of running that test manually from outside the Portage >>> > Brant> sandbox are: >>> > >>> >[...] >>> > >>> > Brant> ++ grep AC_FEATURE_CTYPE stderr >>> > Brant> ++ exit 1 >>> > >>> > Thanks for the report. >>> > >>> >What do tests/testSubDir/stderr and >>> >tests/testSubDir/configure.in contain after the test has failed? >>> > >>> > This is a gentoo configuration problem. The wrapper script really should be bright enough to notice the -o switch and that should imply it should use 2.5, but it is doing the intiuit of what version to use based on the following: # Executes the correct autoconf version. # # - defaults to autoconf-2.13 # - runs autoconf-2.59 if it exists and... # - envvar WANT_AUTOCONF is set to `2.5' # -or- # - configure.ac is present # -or- # - `configure.in' contains AC_PREREQ and the value's 3 first letters # are stringwise greater than '2.13' # -or- # - `configure' is already present and was generated by autoconf greater than # '2.13' # -or- # - `Makefile.in' was generated by automake-1.6 or superior, which # specifically needs autoconf-2.59 # The workaround is to put the following into your environment: WANT_AUTOCONF=2.5; export WANT_AUTOCONF which should fix things. Another possibility which may fail unless you have the latest version of automake would be AUTOCONF=/usr/bin/autoconf-2.59; export AUTOCONF however that will give heartburn to the automake missing tests. Opening a bug report with the gentoo folks may also make sense. -- Mark >> stderr: >> Usage: autoconf [-h] [--help] [-m dir] [--macrodir=dir] >> [-l dir] [--localdir=dir] [--version] [template-file] >> >> >> configure.in: >> stSubDir/configure.in >> AC_INIT >> AC_FEATURE_CTYPE >> AC_FEATURE_ERRNO >> AM_CYGWIN32 >> AM_EXEEXT >> AM_FUNC_MKTIME >> AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL >> AM_MINGW32 >> AM_PROG_INSTALL >> AM_SANITY_CHECK_CC >> AM_SYS_POSIX_TERMIOS >> fp_FUNC_FNMATCH >> fp_PROG_INSTALL >> md_TYPE_PTRDIFF_T >> >> >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBfm7x3x41pRYZE/gRAueHAJwOgGmqZG2ylDpmgZnq+KRqNacthACeLwCT x2DSw9hPo1BPSlVXHxi3Nsw= =GzRn -----END PGP SIGNATURE----- |