Re: Shared library concern

2005-04-26 Thread Andreas Rottmann
FranÃois-Denis Gonthier <[EMAIL PROTECTED]> writes: >> Did you run lintian with -i? Lintian can explain its tags on request. >> It's such a pity this seems to be such an unknown feature... > > Thank you! This was a precious hint. > > I realise I was a bit off on this SONAME thing. Reading the gu

Re: Shared library concern

2005-04-17 Thread François-Denis Gonthier
> Did you run lintian with -i? Lintian can explain its tags on request. > It's such a pity this seems to be such an unknown feature... Thank you! This was a precious hint. I realise I was a bit off on this SONAME thing. Reading the guides and policy manual also made me realise this package ne

Re: Shared library concern

2005-04-17 Thread Justin Pryzby
On Sun, Apr 17, 2005 at 08:43:08PM +0200, Philipp Kern wrote: > On 17 Apr 2005, at 20:24, François-Denis Gonthier wrote: > >The soname doesn't seem to be the problem in that case: > >E: codeblocks: sharedobject-in-library-directory-not-actually-a-shlib > >usr/lib/libcodeblocks.so.1.0-beta6 > > ``1

Re: Shared library concern

2005-04-17 Thread Jeroen van Wolffelaar
On Sun, Apr 17, 2005 at 02:24:16PM -0400, Fran?ois-Denis Gonthier wrote: > On April 17, 2005 08:29 am, Kurt Roeckx wrote: > > > Here the problem is probably that it doesn't have an soname. The > > libcodeblocks.so should be a symlink to the real library. And > > the library itself should get ver

Re: Shared library concern

2005-04-17 Thread Philipp Kern
On 17 Apr 2005, at 20:24, François-Denis Gonthier wrote: The soname doesn't seem to be the problem in that case: E: codeblocks: sharedobject-in-library-directory-not-actually-a-shlib usr/lib/libcodeblocks.so.1.0-beta6 ``1.0-beta6'' is not a SONAME. Please read the Debian Library Packaging Guide.

Re: Shared library concern

2005-04-17 Thread François-Denis Gonthier
On April 17, 2005 08:29 am, Kurt Roeckx wrote: > Here the problem is probably that it doesn't have an soname. The > libcodeblocks.so should be a symlink to the real library. And > the library itself should get version number added to it. > > I suggest you read section 8 of the policy about share

Re: Shared library concern

2005-04-17 Thread Kurt Roeckx
On Sun, Apr 17, 2005 at 02:29:29PM +0200, Kurt Roeckx wrote: > I suggest you read section 8 of the policy about shared > libraries. You may also want to read: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.xml Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subjec

Re: Shared library concern

2005-04-17 Thread Kurt Roeckx
On Sat, Apr 16, 2005 at 01:37:17PM -0400, François-Denis Gonthier wrote: > Hello all, > > I'm having a bit of a concern with a library target Code::Blocks produces > (It's a C/C++ IDE). > > Lintian currently reports: > > E: codeblocks: shlib-with-non-pic-code usr/lib/libcodeblocks.so Shared li

Re: Shared library concern

2005-04-16 Thread Reinhard Tartler
On 4/16/05, François-Denis Gonthier <[EMAIL PROTECTED]> wrote: > I'm having a bit of a concern with a library target Code::Blocks produces > (It's a C/C++ IDE). > > Lintian currently reports: > > E: codeblocks: shlib-with-non-pic-code usr/lib/libcodeblocks.so > E: codeblocks: sharedobject-in-lib

Shared library concern

2005-04-16 Thread François-Denis Gonthier
Hello all, I'm having a bit of a concern with a library target Code::Blocks produces (It's a C/C++ IDE). Lintian currently reports: E: codeblocks: shlib-with-non-pic-code usr/lib/libcodeblocks.so E: codeblocks: sharedobject-in-library-directory-not-actually-a-shlib usr/lib/libcodeblocks.so bu