Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote: Raul Dias [EMAIL PROTECTED] writes: the linker will match them together ? This sounds me a bug in the dynamic linker ? Not in the linker itself, the reason was that the main package and the library were compiled with different

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

Raul Dias [EMAIL PROTECTED] writes: =?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote: Raul Dias [EMAIL PROTECTED] writes: But what do you want exactly, to keep gcc-2.95.3-19cl.src.rpm instead of a newer gcc which provides the same libstdc++-libc6.2-2.so.3 ? No. A newer gcc

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote: Raul Dias [EMAIL PROTECTED] writes: =?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote: Raul Dias [EMAIL PROTECTED] writes: But what do you want exactly, to keep gcc-2.95.3-19cl.src.rpm instead of a newer gcc which

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

Raul Dias [EMAIL PROTECTED] writes: the linker will match them together ? This sounds me a bug in the dynamic linker ? Not in the linker itself, the reason was that the main package and the library were compiled with different (and c++ ABI incompatible) GCCs. This means when you load one

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

On Thu, 7 Mar 2002, Raul Dias wrote: the linker will match them together ? This sounds me a bug in the dynamic linker ? Not in the linker itself, the reason was that the main package and the library were compiled with different (and c++ ABI incompatible) GCCs. 1) Could you please name me

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

Gwenole Beauchesne [EMAIL PROTECTED] wrote: On Thu, 7 Mar 2002, Raul Dias wrote: the linker will match them together ? This sounds me a bug in the dynamic linker ? Not in the linker itself, the reason was that the main package and the library were compiled with different (and c++ ABI

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

Raul Dias [EMAIL PROTECTED] writes: I have proposed a new kind of conflict checking for rpm, but JBJ is not sure (yet) if rpm is the right place for it. However URPMI would be a right tool to check for it. The problem: Using a C++ application compiling with one gcc that depends on

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote: Raul Dias [EMAIL PROTECTED] writes: The problem: Using a C++ application compiling with one gcc that depends on another C++ library that was compiled with another gcc will __not__ work and probably segfaults. This is the main

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

Raul Dias [EMAIL PROTECTED] writes: $ rpm -qR xalan-c | grep libstdc libstdc++-libc6.2-2.so.3 $ ldd /usr/bin/testXPath | grep libstdc libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x4083d000) $ objdump -x /usr/lib/libstdc++-libc6.2-2.so.3 | grep SONAME

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote: Raul Dias [EMAIL PROTECTED] writes: $ rpm -qR xalan-c | grep libstdc libstdc++-libc6.2-2.so.3 $ ldd /usr/bin/testXPath | grep libstdc libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x4083d000) $ objdump

Re: c++ conflicts with urpmi WAS: Re: [Cooker] Cant compile anything that needs Qt

Raul Dias [EMAIL PROTECTED] writes: But what do you want exactly, to keep gcc-2.95.3-19cl.src.rpm instead of a newer gcc which provides the same libstdc++-libc6.2-2.so.3 ? No. A newer gcc would install a different libstdc++ (different soname). This is exactly what we want. What I am