Hi folks, Your work with the gcc-config tool is wonderfull. Thanks a lot! But here is my problem: I want to have the gcc2 and 3 on my gentoo. So I install the gcc-3.2.1-r6 and the gcc-2.95.3-r8 and unmerge gcc-3.2.1 (stable). Everything works fine but some bugs are really anoying: 1- When I make the command: gcc-config "--use-portage-chost X" I have to exit from the terminal (logout) and enter again. Why? Why the env-update doesn't updates the source env. variables? 2- Everytime I made the command "emerge -up world" he says me that I need to downgrade the gcc to gcc-3.2.1. This is 'cause I don't like to live the ~arch flag on. So, I just ignore it. But is VERY anoying. So, I doesn't like to live the ~arch on but I wan't to have gcc2 and 3 with gcc-config working without make some changes (like remove the ~arch and put arch on the gcc-3.2.1-r6 ebuild, ugly but works). I have a suggestion. Put the arch flag instead of the ~arch flag on the gcc-3.2.1-r6 ebuild and put the gcc-3.2.1-r6 on the packages.mask. It is just a suggestion and I don't know if is gonna work. Thanx a lot. Your work are reaching the perfection. Bernardo S. A. Silva
part #1 is valid, part #2 is a bug thats already open
A program cannot modify it's parent environment. Apps cannot update the variables auotmatically that way. You can always '. /etc/profile' or 'source /etc/profile' when you or portage runs env-update.
Part #2 is a bug thats already open... ok, but what his number? Part #1: Why the gcc-config doesn't make the source automatic? Thanx... Bernardo S. A. Silva
So... I will reopen it...
A program cannot modify it's parent environment. Therefore... It can't cause the new variables to propagate up to the parents, and thus cannot, due to unix system implimentations, be automatic as you'd like. There are a couple bugs floating around on that other topic. It's coming... 'Sticky.'
