Summary: | sys-devel/kgcc64 should run gcc-config to select itself | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrew Gaffney (RETIRED) <agaffney> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dschridde+gentoobugs, sparc |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrew Gaffney (RETIRED)
2008-12-01 17:50:19 UTC
Looking at the following line in should_we_gcc_config() in toolchain.eclass, it looks like this *should* already work: curr_config=$(env -i ROOT="${ROOT}" gcc-config -c ${CTARGET} 2>&1) || return 0 That of course assumes that CTARGET is set to sparc64-unknown-linux-gnu in the case kgcc64 on sparc with CHOST="sparc-unknown-linux-gnu". I believe I found the problem. The sys-devel/kgcc64 ebuilds define their own pkg_postinst(), so the gcc-compiler_pkg_postinst() never gets called, and that's where the gcc-config logic is. Just adding a call to 'toolchain_pkg_postinst' at the top of kgcc64's pkg_postinst() seems to fix this. It looks like the fix for bug #228157 caused this problem. looks like this was fixed a while ago: 09 Dec 2008; Mark Loeser <halcy0n@gentoo.org> kgcc64-4.1.2.ebuild, kgcc64-4.2.4.ebuild, kgcc64-4.3.1.ebuild, kgcc64-4.3.2.ebuild: Add call back in for toolchain_pkg_postinst, thanks to Andrew Gaffney <agaffney AT gentoo DOT org>; bug #249504 |