Bug#476645: extra information

and now the bug is gone. But it's still there on another machine running a 2.6.24 Kerrnel, although gcc-4.2 lib was installed there also. So I guess during dist-upgrade or such, the bug was introduced. Regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Man

Bug#476645: Extra information (dpkg, ls) as requested

pr 08:11 libgomp.so -> /emul/ia32-linux/usr/lib/libgomp.so.1 With best regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

Bug#476645: multilib is installed also

; 4.2-20070307), gobjc++-4.2 (<< 4.2-20070307), gobjc++-4.2-multilib (<< 4.2-20070307), gobjc-4.2 (<< 4.2-20070307), gobjc-4.2-multilib (<< 4.2-20070307), treelang-4.2 (<< 4.2-20070307) So it seems one of the other is fine, but that seems not to be the case, howeve

Bug#476645: gcc-4.2: -m32 switch broken?

ld: cannot find -lgcc_s collect2: ld gab 1 als Ende-Status zurück I'm not suprised because in the that directory one can find a 32 subdirectory and there one can find the proper files. So this is some kind of problem With best regards Friedrich -- System Information: Debian Release:

Bug#185662: libstdc++5: Illegal instruction on 386 CPUs

Hi Matthias, > For a workaround, please could you try to replace the file > /usr/lib/libstdc++.so.5.0.3 with the file from the gcc-snapshot > package? Thanks. That fixed the problem for me :-) --jochen

Bug#185662: libstdc++5: Illegal instruction on 386 CPUs

Package: libstdc++5 Version: 1:3.2.3-0pre6 Severity: important Using libstdc++5 on a 386 CPU may cause Illegal instruction (SIGILL). Starting program: /usr/bin/python2.2 Program received signal SIGILL, Illegal instruction. [Switching to Thread 16384 (LWP 297)] 0x400d1b7f in std::locale::_Impl::_