On my system, I have many automakes, including 1.10 and 1.11.1, but not 1.10.[1-3]. The libtool-2.2.6 ebuilds only require >=1.10.1, which I satisfied, but libtool fails to build, complaining that it requires 1.10.1. (Actually it requires >=1.10.1 && <1.11) Changing the RDEPEND automake line to: || ( =sys-devel/automake-1.10.1 =sys-devel/automake-1.10.2 =sys-devel/automake-1.10.3 ) ... since the "&& ( dep1 dep2 )" syntax doesn't work :b ... fixes this (and replaces 1.10 with 1.10.3). Reproducible: Always Steps to Reproduce:
# cat /vt/portage/tmp/portage/sys-devel/libtool-2.2.6b/temp/aclocal.out ***** aclocal ***** ***** PWD: /vt/portage/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b/libltdl ***** aclocal -I m4 am-wrapper: /usr/bin/aclocal-1.10 is missing or not executable. Please try emerging the correct version of automake.
libtool-2 works fine with any automake version. the error is a different issue.
the error Peter shows shouldnt happen. if you unmerge automake-1.10 and then unpack libtool manually, you'll see it, but that's because it avoids the dependencies added by autotools.eclass. as for the original report, NEEDINFO as to why you think what you do. actual error log attachments would be useful.
It's a little hard to reproduce since automake-1.10 is no longer in portage (I have 1.9s and older, 1.10 and 1.11.1 ... to reproduce it I hacked a 1.10.2 ebuild to 1.10 -- although originally I had the real old 1.10 and the same error message), NEVERTHELESS :P, from emerge: >>> Unpacking source... >>> Unpacking libtool-2.2.6b.tar.lzma to /var/tmp/portage/sys-devel/libtool-2.2.6b/work * Applying libtool-2.2.6a-tests-locale.patch ... [ ok ] * Removing useless C++ checks ... [ ok ] * Applying libtool-1.5.20-use-linux-version-in-fbsd.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b/libltdl' ... * Running aclocal -I m4 ... [ ok ] * Running true --copy --force --install --automake ... [ ok ] * Running aclocal -I m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] * Running eautoreconf in '/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b' ... * Running aclocal -I libltdl/m4 ... [ ok ] * Running true --copy --force --install --automake ... [ ok ] * Running aclocal -I libltdl/m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-devel/libtool-2.2.6b/temp/automake-4901.out * * ERROR: sys-devel/libtool-2.2.6b failed: * Failed Running automake ! * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 6972: Called eautoreconf * environment, line 4771: Called eautomake * environment, line 4740: Called autotools_run_tool 'automake' '--add-missing' '--copy' * environment, line 4240: Called die * The specific snippet of code: * die "Failed Running $1 !"; .... from temp/automake-4901.out: ***** automake ***** ***** PWD: /var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b ***** automake --add-missing --copy configure.ac:125: require Automake 1.10.1, but have 1.10 ..... and from configure.ac:125: ## ------------------------ ## ## Automake Initialisation. ## ## ------------------------ ## dnl These are bootstrap requirements! Once built, libtool may work with dnl much older releases of autoconf and automake. See release notes. AM_INIT_AUTOMAKE([1.10.1 gnu subdir-objects dist-lzma]) (Either way, there should still be an ebuild notation for "&& (>=dep1 <dep2)" no?)
no, there shouldnt
will be magically resolved once automake-1.11 goes stable ... not worth the effort to address this another way
How else would you resolve dependencies for packages that require something less than dep2 and greater than dep1?
(In reply to comment #6) > will be magically resolved once automake-1.11 goes stable ... not worth the > effort to address this another way > had the same error, fixed by unmerging autoconf, automake, gnuconfig (with -C option) and remerging everything...
(In reply to comment #8) Forgot to add that only emerging the new automake 1.11.1 doesn't solved the problem
(In reply to comment #9) > (In reply to comment #8) > Forgot to add that only emerging the new automake 1.11.1 doesn't solved the > problem > yes it doesn't I can't find solution.
The solution, as far as I can tell, is to manually install =sys-devel/automake-1.10.3 (any 1.10.?) (Or more generally, to update the ebuild as I mentioned, but that's ugly since it doesn't nicely account for future 1.10.4+ automakes :\)
Or doing what behd did in comment #8
(In reply to comment #8) > (In reply to comment #6) > > will be magically resolved once automake-1.11 goes stable ... not worth the > > effort to address this another way > > > > had the same error, fixed by unmerging autoconf, automake, gnuconfig (with -C > option) and remerging everything... > yes, this solution fixed my problem here also emerge -C autoconf automake gnuconfig emerge autoconf automake gnuconfig and libtool is compiling OK
I ran into this when upgrading an old machine from gcc-3.3.x, when I ran the libtool upgrade after configuring the new gcc. Had several versions of autoconf installed, including 1.10 and 1.11.1, but I still got this error. I solved it by simply running: emerge =sys-devel/automake-1.10.2 which upgraded the slotted 1.10. Afterwards, I re-ran the emerge --oneshot -av libtool and it worked without problems. (One thing of note is that I had not yet switched the machine to use the 10.0 profile; rather, I was still running under 2008.0, which may explain why I still had the ebuild for 1.10.2 available... or perhaps not? No matter.) This is basically the same as the solution in Comment #11. Also, another confirmation that automake-1.11 does NOT "magically resolve" the issue. I had it installed, but still had this problem -- from some casual poking around in the libtool-2.2.6b ebuild temp files, it seems to be very picky about 1.10.x and only 1.10.x, so /usr/lib/misc/am-wrapper.sh forces it to use the installed 1.10 binary, instead of the 1.11.x version.
*** Bug 313679 has been marked as a duplicate of this bug. ***
I came across the same problem when I added to make.conf the following line: CFLAGS="-O2 -pipe -mtune=amdfam10" The compilation succeeded when I changed the line to -mtune=k8 GCC version may affect; I use 3.4.6 which comes with the installation CD, because I could not upgrade to 4.* with the first option set above.
*** Bug 314475 has been marked as a duplicate of this bug. ***
Also got bit, updating an old system to new portage version after emerge --sync. Like the fine folks have said above: emerge -vt1 =sys-devel/automake-1.10.3 emerge -vt1 autoconf automake gnuconfig and then it works just fine.
*** Bug 317705 has been marked as a duplicate of this bug. ***
As a note, this one is still biting people. Got caught on this one just now for libtool2.2.6b, but at least the workaround was here. Thx, folks!
*** Bug 325807 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > will be magically resolved once automake-1.11 goes stable ... not worth the > effort to address this another way > it's stable now, shouldn't we change autotools.eclass to prefer 1.11 ? or was that already done...
libtool-2.2.6b and libtool-2.2.10 block =automake-1.10, and autotools.eclass requires automake-1.11 now
I am experiencing the same bug with automake-1.11.1 when trying to update two old systems. The unmerge/re-emerge workaround mentioned in comment 13 isn't working. emerge info: Portage 12175-svn (default/linux/x86/10.0/server, gcc-4.1.1, glibc-2.4-r4, 2.6.17-gentoo-r7 i686) ================================================================= System uname: Linux-2.6.17-gentoo-r7-i686-Pentium_II_-Deschutes-with-glibc2.0 Timestamp of tree: Sun, 06 Feb 2011 05:00:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.1_p17 dev-lang/python: 2.4.3-r4 dev-util/ccache: 2.4-r6 sys-apps/baselayout: 1.12.6 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.65-r1 sys-devel/automake: 1.11.1 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc: 4.1.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 sys-devel/make: 3.81 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=i686 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-march=i686 -O2 -fomit-frame-pointer -pipe -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks metadata-transfer parallel-fetch sandbox userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.netnitco.net http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LDFLAGS="-Wl,-O1 -Wl,--sort-common -s" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync_excludes" 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 --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="acl berkdb bzip2 cli cracklib crypt cxx dri fortran gdbm gpm iconv modules mudflap ncurses nls nptl nptlonly openmp pam pcre pppd readline session snmp ssl sysfs tcpd truetype x86 zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" PHP_TARGETS="php5-3" RUBY_TARGETS="ruby18" USERLAND="GNU" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS error: make[3]: Leaving directory `/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b' make[2]: Leaving directory `/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b' make[1]: Leaving directory `/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b' /usr/lib/portage/bin/doman: line 35: unexpected argument `(' to conditional binary operator /usr/lib/portage/bin/doman: line 35: syntax error near `(.' /usr/lib/portage/bin/doman: line 35: ` [[ $x =~ (.*)\.([a-z][a-z](_[A-Z][A-Z])?)\.(.*) ]] ; then' * * ERROR: sys-devel/libtool-2.2.6b failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 3146: Called die * The specific snippet of code: * doman ${x}.1 || die; * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-devel:libtool-2.2.6b:20110206-085125.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-2.2.6b/temp/environment'.
(In reply to comment #24) > I am experiencing the same bug with automake-1.11.1 when trying to update two > old systems. The unmerge/re-emerge workaround mentioned in comment 13 isn't > working. No. Nothing in the output you provided indicates it's the same bug. But your system looks *BADLY* outdated. Try upgrading to latest stable portage. If the problem persists, open a new bug instead. Likely culprits: > Portage 12175-svn (default/linux/x86/10.0/server, gcc-4.1.1, glibc-2.4-r4, Too old portage. > app-shells/bash: 3.1_p17 Too old bash.
