Package: linda
Version: 0.3.10
Severity: normal

Hello,

Running linda over a test .deb compiled from the attached tar.gz file produces
(among others) the following errors:

E: foo; Object /usr/lib/foo/foo.o is not directly linked against libc.
 The binary object shown above is not directly linked against the
 required library libc.so.6.
W: foo; Shared binary object /usr/lib/foo/foo.o has no dependancy information.
 The binary object listed above is a shared object, but does not report
 that it depends on any other shared libraries.

The object file foo.o is generated with "gcc -Wall -c -g -O2 test.c".
The problem is that object files should not, and in fact cannot, be linked
against external libraries, so these linda errors make no sense.  Please
see Justin Pryzby's analysis here:
http://lists.debian.org/debian-mentors/2005/03/msg00358.html

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.8-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linda depends on:
ii  binutils                      2.15-5     The GNU assembler, linker and bina
ii  dash                          0.5.2-2    The Debian Almquist Shell
ii  file                          4.12-1     Determines file type using "magic"
ii  man-db                        2.4.2-21   The on-line manual pager
ii  python                        2.3.5-2    An interactive high-level object-o

-- no debconf information

regards,

-- 
Kevin B. McCarty <[EMAIL PROTECTED]>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG public key ID: 4F83C751                 Princeton, NJ 08544

Attachment: foo_0.0.1.tar.gz
Description: Binary data

Reply via email to