Debian Bug report logs - #558872
libcgic: unresolved symbol cgiMain

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Peter Fritzsche <peter.fritzsche@gmx.de>

To: maintonly@bugs.debian.org

Subject: Resolve unresolved symbols in shared libraries

Date: Mon, 30 Nov 2009 19:32:34 +0100

Source: libcgic
Version: 2.05-2
Severity: wishlist
User: peter.fritzsche@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems.... but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzsche@gmx.de;tag=no-add-needed

More informations can be found at
 http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol cgiMain used by debian/libcgic2/usr/lib/libcgic.so.2.05 found in none of the libraries.

Message #10 received at 558872@bugs.debian.org (full text, mbox, reply):

From: Colin Watson <cjwatson@debian.org>

To: Peter Fritzsche <peter.fritzsche@gmx.de>

Cc: 558872@bugs.debian.org

Subject: Re: Resolve unresolved symbols in shared libraries

Date: Mon, 13 Dec 2010 15:18:29 +0000

On Mon, Nov 30, 2009 at 07:32:34PM +0100, Peter Fritzsche wrote:
> I build all packages some time ago with binutils-gold and your package build
> without an hard failure, but I noticed that you seems to provide a library in
> a specific library package so other packages can link against it without
> problems.... but your shared object has still some unresolved symbols which
> the program which links agaomst it must resolve. This isnt a good idea because
> when you introduce new dependencies the package previously linked against the
> old version will break because it doesnt know about the new dependency.
> Maybe you could link against all needed libraries so programs must not link
> against libraries which it doesnt need to use.
[...]
> dpkg-shlibdeps: warning: symbol cgiMain used by debian/libcgic2/usr/lib/libcgic.so.2.05 found in none of the libraries.

This is a slightly odd library: it requires the *application* to define
a cgiMain symbol.  This warning is therefore a false positive for
libcgic.

-- 
Colin Watson                                       [cjwatson@debian.org]

Message #19 received at 558872-done@bugs.debian.org (full text, mbox, reply):

From: Bart Martens <bartm@debian.org>

To: 558872-done@bugs.debian.org

Subject: libcgic: unresolved symbol cgiMain

Date: Sun, 9 Sep 2012 10:01:50 +0000

Colin Watson explained this on 13 Dec 2010 :
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;bug=558872

Send a report that this bug log contains spam.