[Slackbuilds-users] Problem with libsigc++-2.2.9-i486-1_SBo.tgz

David Woodfall dave at dawoodfall.net
Fri Oct 28 15:51:11 UTC 2011

On (06:56 28/10/11), Graham Lawrence <gl00637 at gmail.com> put forth the proposition:
>Attempt to compile nzbget-0.7.0 failed in ./configure with message
>configure: error: "libsigc++-2.0 header files not found"
>So I got the dependencies, including libsigc++-2.2.9, and installed
>them, apparently all good.
>But compiling nzbget again failed at same place.  To check, I did
>root at a:/usr/pkgs# ls
>HandBrake-0.9.5-i686-1_SBo.tgz  libpar2-0.2-i486-1_SBo.tgz
>root at a:/usr/pkgs# installpkg  libsigc++-2.2.9-i486-1_SBo.tgz
>Verifying package libsigc++-2.2.9-i486-1_SBo.tgz.
>Installing package libsigc++-2.2.9-i486-1_SBo.tgz:
># libsigc++ (typesafe callback system for standard C++)
># libsigc++ implements a typesafe callback system for standard C++.
># It allows you to define signals and to connect those signals to any
># callback function, either global or a member function, regardless
># of whether it is static or virtual.
># It also contains adaptor classes for connection of dissimilar
># callbacks and has an ease of use unmatched by other C++ callback
># libraries. Libsigc++ is licensed under the GNU Library General
># Public License, LGPL.
>Executing install script for libsigc++-2.2.9-i486-1_SBo.tgz.
>Package libsigc++-2.2.9-i486-1_SBo.tgz installed.
>root at a:/usr/pkgs# updatedb
>root at a:/usr/pkgs# locate libsigc++-2*

Try with quotes or the * will wildcard the current directory.

locate "*sigc++-2*"

>root at a:/usr/pkgs# echo $PATH
>root at a:/usr/pkgs#
>I'm not familiar with this process, but it seems to me there should
>now be at least 2 occurrences of the name libsigc++-2* on my system,
>one of them in the PATH?

PATH is only for binaries not libraries.
The libs will be in /usr/lib so you can

ls /usr/lib/*sigc*

The headers will be in /usr/include:

ls /usr/include/sigc++-2.0/*/*

You may want to look at the mzbget Makefile or configure to see what's
up, unless someone here knows a fix firsthand.


>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - http://slackbuilds.org/faq/

Don't look back, the lemmings are gaining on you.

More information about the SlackBuilds-users mailing list