lintian problem [shared-lib-without-dependency-information]

2006-01-09 Thread Székelyi Szabolcs

Hi,

I'm trying to make my first package... Everything goes fine except one 
thing. Lintian says:


W: libvrb0: shared-lib-without-dependency-information 
./usr/lib/libvrb.so.0.4.0


I understand what this means, know how to fix it (by adding -lc to ld 
arguments). Unfortunately the upstream source uses some strange 
(non-auto{make,conf}) build system, meaning (among other things) that 
the arguments of ld are hard-coded into the configure script.


Solutions may be:
* modifying the configure script
* manually adding libc to 'Depends:' line
* overriding the warning

Which one sould I choose? Any other idea?

The upstream source is available from http://vrb.slashusr.org/

Thanks for your help,
--
Sze'kelyi Szabolcs


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: lintian problem [shared-lib-without-dependency-information]

2006-01-09 Thread Russ Allbery
Székelyi Szabolcs [EMAIL PROTECTED] writes:

 I'm trying to make my first package... Everything goes fine except one
 thing. Lintian says:

 W: libvrb0: shared-lib-without-dependency-information 
 ./usr/lib/libvrb.so.0.4.0

 I understand what this means, know how to fix it (by adding -lc to ld
 arguments). Unfortunately the upstream source uses some strange
 (non-auto{make,conf}) build system, meaning (among other things) that
 the arguments of ld are hard-coded into the configure script.

You really shouldn't have to add -lc to the ld arguments; that indicates
that upstream is doing something very odd.

 Solutions may be:
 * modifying the configure script
 * manually adding libc to 'Depends:' line
 * overriding the warning

 Which one sould I choose? Any other idea?

 The upstream source is available from http://vrb.slashusr.org/

Upstream is explicitly writing out a Makefile that links the library with
-nostdlib -nostartfiles, despite the fact that the library calls libc
functions.  This is broken.  I'm not sure about the -nostartfiles,
although that seems very suspicious, but -nostdlib is simply wrong and
should be removed so far as I can tell.

You may want to ask upstream why they did that, but I'd patch Configure to
remove -nostdlib in the maketop function that writes out the Makefile.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/