Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 100531 - dev-util/pkgconfig-0.18.1-r1 depends on automake-1.7*
Summary: dev-util/pkgconfig-0.18.1-r1 depends on automake-1.7*
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-27 16:50 UTC by Erik Bergmann
Modified: 2005-08-02 02:03 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Bergmann 2005-07-27 16:50:27 UTC
I tried to install dev-util/pkgconfig-0.18.1-r1 but got
* Running automake
am-wrapper: /usr/bin/automake-1.7 is missing or not executable.
            Please try emerging the correct version of automake.

emerge =automake-1.7.9-r1 solved it.
Please fix dependencies

Reproducible: Always
Steps to Reproduce:
1. unemerge your current automake-1.7*
2. emerge pkgconfig
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-07-27 19:20:26 UTC
You are not supposed to unmerge automake versions; automake-wrapper RDEPENDs on
automake-1.7*, so there is no need for pkgconfig to depend on it, it should be
always installed.

P.S. If this problem occured during a fresh install, then see Bug 99819.
Comment 2 Erik Bergmann 2005-07-28 02:20:38 UTC
I have never unemerged any version of autmake.
This happened on a system I set up in january.
It wasnt in use for 7 month and automake-1.7* was not installed.
Comment 3 Simon Stelling (RETIRED) gentoo-dev 2005-07-28 02:30:43 UTC
you probably once used emerge -P which removed older versions of automake.
anyway, just re-merge automake-wrapper and it will be fixed. and automake will
be in dependencies for reasons jakub already explained
Comment 4 Albert Holm 2005-08-02 02:01:12 UTC
I bootstrapped a 2005.0 system yesterday and ran into this problem during emerge 
--emptytree system. Solved it the same way.
Comment 5 Albert Holm 2005-08-02 02:03:48 UTC
Sorry for comment #4, did not see the closed bug for fresh systems because it 
was striked out.