=?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 -x /usr/lib/libstdc++-libc6.2-2.so.3 | grep SONAME
>> > SONAME libstdc++-libc6.2-2.so.3
>> >
>> >How can we known more here ?
>>
>> I will use qt2 as an example:
>>
>> $ rpm -qR qt2 | grep libstd
>> libstdc++-libc6.2-2.so.3
>>
>> $ rpm -q --whatprovides $(rpm -qR qt2 | grep libstd)
>> libstdc++-2.95.3-19cl
>>
>> and of course, if you want to know which gcc generated this (not really needed):
>>
>> $ rpm -q $(rpm -q --whatprovides $(rpm -qR qt2 | grep libstd) ) --qf
>"%{SOURCERPM}\n"
>> gcc-2.95.3-19cl.src.rpm
>>
>> Btw, I did this on a CL system, not mdk. But the results should be equivalent.
>
>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).
What I am suggesting is a way to let urpmi detect when a c++ application package
will not work before installing them.
>
>If this is not running because of incompatible library used, the so name should
>be changed ? no ?
Yes, and it is changed.
- Raul Dias
