Summary: | on stage 1 install emerge -e system dies on pkgconfig due to missing automake dep | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lance Lucas <llucas> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amd64, austin.grossman |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lance Lucas
2005-07-21 11:14:10 UTC
my mistake, i of course meant when moving from stage2 to stage3. autotools are in base, pkgconfig isn't. I'm not quite sure how this could happen ? reporter: were you able to reproduce this? Unfortunately, the machine suffered a hardware failure not long after my report. M/B is currently under RMA to Giga-byte. Will look into again when hardware is back....apologies to all. I ran into this too when bootstrapping from 2005.0 yesterday. Unfortunately I resolved the problem to continue merging system during night so logs are gone and emerge --info is no longer correct with regards to version numbers. *** Bug 101103 has been marked as a duplicate of this bug. *** looks like a few others have come across this too...so i'll reopen as the other was marked as a dup. Apparently there are packages in the base profile (or packages implicitly brought by the default USE flags) that depend on pkgconfig, which could be causing this. I've added automake as a dependency in the relevant ebuild. If it's possible, it'd be nice if someone could test this on a clean system and let us know the result. Thanks. no activity for over two weeks, any objections to marking as resolved? this fix would have undoubtedly fixed my problem, and it appears no one else is running into it thanks to the fix. nope :) |