Summary: | Emerge failure on gnome-spell-0.4.1-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark Rickard <mrickard> |
Component: | [OLD] GNOME | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.1a | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mark Rickard
2002-04-26 21:15:42 UTC
gcc 3? No, gcc-2.95.3-r5 is the compiler. It is a normal Gentoo 1.1a install on x86 except the system is built on binutils-2.12.90.0.4, not on the standard binutils-2.11.92.0.12.3 in the default-1.0 profile. Mark Hi, try binutils-2.12.90.7, as gnome-spell works fine here with it. Switching to the latest binutils-2.12.90.0.7 doesn't change anything. It is definitely a problem with libasound. I don't understand why libasound is needed for gnome-spell. The only time I get this, is with gcc-3.0.4. Also, are you using alsa-0.9? I was using the alsa 0.9 beta when I first tried to emerge gnome-spell. I removed those and reinstalled alsa 0.5. Emerge gnome-spell failed with the exact same error. Finally, I emerged the new alsa 0.9 release candidate 1, tried to emerge gnome-spell, and got the same error once again. Mark Ok, here is your problem: the build looks for libstdc++ here: /usr/local/lib/libstdc++.so Any idea why ? I compiled and installed gcc 3.0.4 from source (not using emerge) into /usr/local because I need the gcc 3.x compiler for some Fortran code. gcc invokes gcc 2.95.3, and I have to call gcc 3.0.4 explicitly using /usr/local/bin/gcc. As far as I know, it is not possible to have gcc 2.95.3 and gcc 3.x simultaneously installed using portage. This setup (gcc 2.95.3 in /usr and gcc 3.0.4 in /usr/local) has never caused any problems before, so I'm not sure why it would start now. Mark Ok, this makes sense. You should have a /usr/local/lib/libstdc++.la. Move it out of there, as libtool incorrectly uses this for gcc-2.95.3. Another option is to use our gcc-3.0.4 ebuild, as it do not have this problem (I have both installed). If you do, remember to clear out /usr/local/. Should be fixed i guess. |