Bug 160279 – sys-devel/autoconf-wrapper-4-r3 doesn't try to autodetect the correct version unless WANT_AUTOMAKE is set

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description David Leverton 2007-01-05 08:18:36 UTC]

When trying to run autoconf for a autoconf 2.1 package (outside of Portage, BTW) with no special environment variables set, autoconf-wrapper tries to use autoconf 2.5 (or higher) instead.  With WANT_AUTOMAKE set to a suitably low value, it correctly discovers that the package needs autoconf 2.1 (even if the package doesn't actually use automake).

Portage 2.1.1-r2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r4, 2.6.18-gentoo-r4 x86_64)
=================================================================
System uname: 2.6.18-gentoo-r4 x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-50
Gentoo Base System version 1.12.6
Last Sync: Thu, 04 Jan 2007 19:30:01 +0000
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -msse3 -pipe -fomit-frame-pointer -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/share/games/angband/apex /var/games"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-march=athlon64 -msse3 -pipe -fomit-frame-pointer -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig candy ccache collision-protect distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.tiscali.nl/ http://ftp.heanet.ie/pub/gentoo/ http://gentoo.blueyonder.co.uk"
LC_ALL="en_GB.UTF-8"
LINGUAS="en_GB en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/overlays/gentoo-haskell /usr/local/overlays/xeffects"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 aac aalib acl acpi alsa alsa_cards_hda-intel alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol apache2 arts audiofile bash-completion bzip2 cairo cdr dbus dlloader dri dvd dvdr elibc_glibc fam gif gstreamer gtk2 hal input_devices_keyboard input_devices_mouse input_devices_synaptics jack jpeg kde kdehiddenvisibility kernel_linux lcms libcaca linguas_en linguas_en_GB mad mbox mng mp3 mpeg nls nptl nptlonly nvidia ogg pam png readline samba speex ssl svg timidity truetype udev unicode userland_GNU video_cards_nv video_cards_nvidia vorbis xpm xv xvid xvmc zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS

[Comment 1 Jakub Moc (RETIRED) 2007-01-05 09:49:50 UTC]

(In reply to comment #0)
> When trying to run autoconf for a autoconf 2.1 package (outside of Portage,
> BTW) with no special environment variables set, autoconf-wrapper tries to use
> autoconf 2.5 (or higher) instead.  

Yes, that's a correct and expected behaviour.