| 1 |
I went from a bootstrapped gcc3 profile with gcc3.0.4 to gcc3.1. Some |
| 2 |
stuff I've seen break so far: |
| 3 |
|
| 4 |
gtkmm: |
| 5 |
wouldn't compile without patch. fixed in portage cvs though (unmask |
| 6 |
x11-libs/gtkmm-1.2.9-r1 and test it for me) |
| 7 |
|
| 8 |
galeon: |
| 9 |
similar situation. soon to be fixed in portage cvs (will be 1.2.1-r2 |
| 10 |
when i commit it shortly -- test that too if you can) |
| 11 |
|
| 12 |
If some kind volunteers could test these two items with gcc2.95.3, |
| 13 |
gcc3.0.4 and gcc3.1 and let me or some other dev know if they work for |
| 14 |
each, we'll unmask them. |
| 15 |
|
| 16 |
Appart from that, I've found you need to re-emerge basically any package |
| 17 |
who's libs or binaries depend on libstdc++.so.3. (c++-based apps). |
| 18 |
|
| 19 |
I'll post more stuff to this thread as I find it. And, no... I haven't |
| 20 |
tried KDE/QT with gcc3.1 yet :) |
| 21 |
|
| 22 |
Matt |
| 23 |
|
| 24 |
On Mon, 2002-05-20 at 17:24, Milos Negovanovic wrote: |
| 25 |
> when can we expect switch to gcc3?...just curious |
| 26 |
|
| 27 |
-- |
| 28 |
Matthew Kennedy |
| 29 |
Gentoo Linux Developer |
Archives