Summary: | sys-devel/automake-wrapper seems to be broken | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Palagin Alex <palagin> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alonbl, chutz+bugs.gentoo.org, frank_meier, grobian, paulo |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | automake-wrapper-default-exists.patch |
Description
Palagin Alex
2006-11-07 06:23:45 UTC
the symlinks are correct Same for me... If automake-1.10 is not installed autoreconf does not work: $ autoreconf -i -v am-wrapper: /usr/bin/aclocal-1.10 is missing or not executable. Please try emerging the correct version of automake. am-wrapper: /usr/bin/automake-1.10 is missing or not executable. Please try emerging the correct version of automake. autoreconf-2.60: Entering directory `.' autoreconf-2.60: configure.ac: not using Gettext autoreconf-2.60: running: aclocal --output=aclocal.m4t am-wrapper: /usr/bin/aclocal-1.10 is missing or not executable. Please try emerging the correct version of automake. autoreconf-2.60: aclocal failed with exit status: 1 Workaround: $ WANT_AUTOMAKE="1.9" autoreconf -i -v Same here x86, automake-wrapper-2 (marked stable) installs script /usr/bin/automake which directs by default to automake-1.10 which is not marked stable. This creates a whole lot of mess! :-\ that's already fixed in latest version, i just need to commit a small backport to stable What do you mean by latest version? Just synced and latest stable is still automake-wrapper-2. Forget it... re-read your msg... and I got it now! :-) You still have to mark it stable! heh so, what's up with this, when will 1.10 be marked as stable? tumbled over this in the last hour. Why doesn't the automake wrapper simply default to the latest available version? And shouldn't it have automake in its RDEPEND? base-system: Can someone solve this issue? I think this is a critical stable issue, that needs to be solved. Created attachment 101577 [details, diff]
automake-wrapper-default-exists.patch
How is this for a solution. Make the wrapper default to the highest version of an automake executable and it also gives a proper warning if no executables are found.
Comment on attachment 101577 [details, diff]
automake-wrapper-default-exists.patch
i said it was fixed already in newer versions
fixed in cvs |