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