ebuild compile prefixes roots regular path to gcc, this interferes with a wrapper I use on my system (eg /usr/local/bin/gcc) and isnt the behaviour I expected.
HUH ?
My interpretation: He wants 'ebuild compile' to use /usr/local/bin/gcc as opposed to one that, according to him, is place into $PATH before his /usr/local/bin edition. At line 45 in ebuild.sh it replaces PATH in the environment. That's most likely his problem. Any particular reason we have to reorder the path that way?
I think we should check with Daniel ... it could be some newbie common made mistake he "fixed" back in the days.
Azarah, you should know the answer to this -- in /etc/profile, we add the "canonical" (standard) paths manually to ROOTPATH.... Because ebuild.sh needs to add any new paths to its list of paths, it needs to do an env-update when it starts up. It then sources /etc/profile.env and then sets path similarly to how it is set in /etc/profile, except with the addition of /usr/lib/portage/bin. So, if Luke wants to be able to sneak a path in before the official paths, then the best solution is likely to involve changing how we handle /etc/profile: move /usr/bin:/bin:/usr/sbin:/sbin from /etc/profile to 00basic, and then he'll have some control over the order. Does this sound like a good or bad idea?
Daniel, we do change the PATH in ebuild.sh: -------------------------------------------------------- source /etc/profile.env > /dev/null 2>&1 export PATH="/sbin:/usr/sbin:/usr/lib/portage/bin:/bin:/usr/bin:${ROOTPATH}" if [ -e /etc/init.d/functions.sh ] -------------------------------------------------------- Maybe just add /usr/lib/portage/bin to that, and the rest *after* $ROOTPATH ?
Will this ever be fixed?? I would really appreciate it.
Well, it should be fixed portage side. Any reason to use a diff gcc ? We need help to get the gcc profile scheme improved if you have a setup that are not supported ...
I use a proprietary wrapper that allows distributed compilation.
portage-2.0.47-r2 will have 'PREROOTPATH' that can be defined and will be prepended to the PATH in ebuild.sh Further integration later.
Thank you.
