On Sat, Aug 06, 2005 at 08:52:24PM +0200, Mattia Dongili wrote: > On Sat, Aug 06, 2005 at 09:34:37AM -0700, Steve Langasek wrote: > > On Sat, Aug 06, 2005 at 02:28:32PM +0200, Mattia Dongili wrote: > > > On Sat, Aug 06, 2005 at 01:01:12PM +0200, Ghe Rivero wrote: > > > [...] > > > > Apart of this, i also hve python bindings: > > > > python2.3-libsome: > > > > /usr/lib/python2.3/site-packages/libsomemodule.la > > > > /usr/lib/python2.3/site-packages/libsome.so > > > > > > And i have this on lintian: > > > > > > W: python2.3-libsome: package-name-doesnt-match-sonames libsomemodule.so > > > > > I have the same with cpufreqd, I think the warning in this cases > > > (/usr/lib/<application> with "architecture-dependent data exclusively > > > used by the application" -FHS 4.4-) should be suppressed. > > > > Such modules shouldn't actually have SONAMEs at all; perhaps fixing the > > build to not include an SONAME for something that isn't a shared library > > would make this warning go away. > Ok, I've been reading docs for a while now... can anybody help on how to > avoid SONAME using libtool and friends? (I'm already giving it the > -module and -avoid-version flags but it still links with -Wl,-soname > -Wl,cpufreqd_blabla.so) If libtool is setting an SONAME when you build with -module, then I guess this would be a bug in the version of libtool you're using. Cheers, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature