Guillaume Rousse <[EMAIL PROTECTED]> writes:
> When using rpmoint on recent packages i made from wolfpack, i have this on
> lib rpm :
> W: libY2 no-soname /usr/lib/libY2.so.12
> W: libY2 devel-file-in-non-devel-package /usr/lib/libY2.so
>
> The situation is there is only a dynamic lib file, with only minor number,
> and one link to it, with just .so suffix
> /usr/lib/libY2.so
> /usr/lib/libY2.so.12
> I could put the .so in devel package to please rpmlint, but that sounds
> stupid. And what about the first message ?
Each library has a soname. This name fully qualifies the name and version
of the lib, according to future dependencies handling. To check a soname,
do:
[gc@bi ~] objdump -x /usr/lib/libbonobo.so | grep SONAME
SONAME libbonobo.so.2
The number is called the major number of the library. It indicates binary
compatibility between versions.
The first warning says to you that the library does not contain the SONAME
tag. This is because the ld call that created the dynamic library did not
contain the parameter "-soname" to set the soname. This is generally done
through gcc with the following parameter: "-Wl,-soname,libbonobo.so.2".
The second warning you understand :-).
HaPpy TraKT0p3l!
http://us.mandrakesoft.com/~gc/tracto/
