Probably this sequence needs appropriate c-flags changing in make.conf file
after each switching (if I use different ones for 4.3 and <4.3). Doesn't
it?
=== On Monday 11 August 2008, Jan Schneiders wrote: ===
> You can put gcc 4.1 in a slot on your system and choose to compile
> programs
You can put gcc 4.1 in a slot on your system and choose to compile
programs that don't work with the newest version, with the old version:
# emerge -av sys-devel/gcc:4.1 (you may have to unmask: "echo "=sys-
devel/gcc-4.1.2 ~x86" >> /etc/portage/package.keywords)
# gcc-config -l
# gcc-config
2008/8/11, Peter Wood <[EMAIL PROTECTED]>:
> I don't really mind using the ~x86 version of these packages, but wonder why
> the old, stable packages won't compile with a newer gcc. Isn't gcc supposed
> to be downward compatible?
>
No, take a look here:
http://bugs.gentoo.org/show_bug.cgi?id=198121
Hi list,
A few days ago I upgraded gcc from 4.1.2 to 4.3.1-r1 (upgrading
Eclipse-sdk to the latest ~x86 version made installing gcc 4.3.1-r1
necessary, so I thought I would stick with it on my test box).
Now I am re-emerging world and have noticed that a number of packages
which compiled fine
4 matches
Mail list logo
