| 1 |
> BTW, I use FEATURES=buildpkg, so after initial compile, switching glibcs |
| 2 |
> back to the old gentoo approved 2.3.5-rX compiled with a gentoo approved |
| 3 |
> gcc-3.4.4, is simply a matter of emerge -K-ing the desired glibc. That's |
| 4 |
> really the only reason I'm daring enough to be running the still |
| 5 |
> hard-masked snapshot in the first place. With emerge -K, it's almost as |
| 6 |
> simple as a glibc-config, parallel to gcc-config, would be, and in some |
| 7 |
> ways less problematic, given the fact that since I've compiled KDE against |
| 8 |
> gcc-4's libstdc++, every time I gcc-config back to 3.4.x, certain KDE apps |
| 9 |
> (generally, anything using khtml, so not only Konqueror, but kweather, |
| 10 |
> and a few others) refuse to work correctly, until I gcc-config back to a |
| 11 |
> gcc-4.x once again. |
| 12 |
|
| 13 |
Yeah... uh... that's a known PITA issue... HOPEFULLY everything |
| 14 |
compiled against the 3.4 libstdc++ should work with the 4.0 libstdc++. |
| 15 |
You can get around this particular issue by |
| 16 |
creating /etc/env.d/01usegcc4stdcpp to force the loader to use the gcc4 |
| 17 |
libs: |
| 18 |
LDPATH=/usr/lib/gcc/x86_64-pc-linux-gnu/4.0.1:/usr/lib/gcc/x86_64-pc-linux-gnu/4.0.1/32 |
| 19 |
|
| 20 |
Then run env-update |
| 21 |
|
| 22 |
You can check that it's using the gcc4 libstdc++ by doing: |
| 23 |
ldd /usr/kde/3.4/bin/konqueror | grep stdc++ |
Archives