| 1 |
You can put gcc 4.1 in a slot on your system and choose to compile |
| 2 |
programs that don't work with the newest version, with the old version: |
| 3 |
|
| 4 |
# emerge -av sys-devel/gcc:4.1 (you may have to unmask: "echo "=sys- |
| 5 |
devel/gcc-4.1.2 ~x86" >> /etc/portage/package.keywords) |
| 6 |
# gcc-config -l |
| 7 |
# gcc-config x86_64-pc-linux-gnu-4.1.2 |
| 8 |
# source /etc/profile |
| 9 |
|
| 10 |
If you want to go back to the new version, just do again: |
| 11 |
|
| 12 |
# gcc-config -l |
| 13 |
# gcc-config x86_64-pc-linux-gnu-4.3.1-r1 |
| 14 |
# source /etc/profile |
| 15 |
|
| 16 |
|
| 17 |
On Aug 11, 2008, at 3:58 PM, Daniel Pielmeier wrote: |
| 18 |
|
| 19 |
> 2008/8/11, Peter Wood <p2wood@×××××××××.ca>: |
| 20 |
>> I don't really mind using the ~x86 version of these packages, but |
| 21 |
>> wonder why |
| 22 |
>> the old, stable packages won't compile with a newer gcc. Isn't gcc |
| 23 |
>> supposed |
| 24 |
>> to be downward compatible? |
| 25 |
>> |
| 26 |
> |
| 27 |
> No, take a look here: |
| 28 |
> http://bugs.gentoo.org/show_bug.cgi?id=198121 |
| 29 |
> |
Archives