Summary: | gcc-config does not tell about source /etc/profile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lars Weiler (RETIRED) <pylon> |
Component: | [OLD] GCC Porting | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2004.1 | ||
Hardware: | PPC | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lars Weiler (RETIRED)
2004-06-18 00:52:56 UTC
i'm going to guess and say that this is because when you finished emerging gcc it ran `gcc-config` for you to the new 3.4.0 This could be true, although /usr/bin/gcc --version showed that this is gcc-3.3.3. Probably gcc-config ran, but source /etc/profile has not been called (and the einfo does not tell about that, too). that's because *you* have to call `source /etc/profile` ... there is no way (that i know of) to push environment changes into a shell without the user doing it the einfo to tell you to `source /etc/profile` was probably lost at the end of the emerge ... in other words, perhaps this is really just a dupe of the portage einfo logging bug Nope, initially I didn't hat the intension for "I have just one more comment about emerge logging". And if you had looked into the gcc-3.4-ebuild you would knew that there is no information about calling `source /etc/profile` manually. Nevertheless, as nobody will take care for it and probably more users will send bugs as soon as gcc-3.4 becomes stable, I will resolve this bug as worksforme during the meantime. i know theres no info about 'source /etc/profile' in the ebuild it's because the ebuild calls gcc-config which should print out the info about sourcing /etc/profile In pkg_postinst(), which should be last thing you see after its been merged if I am not mistaken ... |