Summary: | gcc version used in compile no longer detectable in emerged package information | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | DrChandra the Gentoo Person <gentooperson> |
Component: | Eclasses | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | gentoo.integer, kingjon3377 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
DrChandra the Gentoo Person
2008-04-17 16:33:01 UTC
I guess we can have portage export it. It would be a bit nicer if we could fit it into one of the toolchain eclasses somehow, but maybe that won't be able to cover all the necessary cases. i'm not sure putting into a toolchain eclass would work as then every ebuild out there would have to explicitly inherit it :/ if you're looking to simply setup some dummy vars for users to hook off of via a sneaky backdoor, then it should be 4 fold: PORTAGE_CC_VERSION=$(${CC:-gcc} --version | head -n1) PORTAGE_CBUILD_VERSION=$(${CBUILD}${CBUILD+-}${CC:-gcc} --version | head -n1) PORTAGE_CHOST_VERSION=$(${CHOST}${CHOST+-}${CC:-gcc} --version | head -n1) PORTAGE_CTARGET_VERSION=$(${CTARGET}${CTARGET+-}${CC:-gcc} --version | head -n1) *** Bug 238048 has been marked as a duplicate of this bug. *** Nothing for toolchain to do here... With gcc-5.3.0 being unstable now the question rises here again how to include that info into "emerge --info" |