pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
pkg/42048: lang/gambc can't find -lgambc during install phase (NetBSD 4.0/i386)
>Number: 42048
>Category: pkg
>Synopsis: lang/gambc can't find -lgambc during install phase (NetBSD
>4.0/i386)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: pkg-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Sep 11 10:30:00 +0000 2009
>Originator: Robert Elz
>Release: NetBSD 4.0 / i386 pkgsrc current 2009-09-10
>Organization:
Prince of Songkla University
>Environment:
System: NetBSD jade.coe.psu.ac.th 4.0_STABLE NetBSD 4.0_STABLE
(JADE-1.696-20080517) #9: Fri May 23 18:55:13 ICT 2008
kre%jade.coe.psu.ac.th@localhost:/usr/obj/4/kernels/JADE i386
Architecture: i386
Machine: i386
>Description:
A link command run during the install phase of lang/gambc (gambc-4.2.8)
fails to find -lgambc (I don't see it actually referenced on the
command line printed by gmake that way - but these days I never
really believe the output from any make ...)
>How-To-Repeat:
I use pkg_comp with libkver and NetBSD 4.0 release sets (except x*
sets, I use pkgsrc modular xorg). I doubt any of that is particularly
relevant to this problem.
In that environment I see ...
making install in gsi
gmake[1]: Entering directory
`/pkg_comp/obj/pkgsrc/lang/gambc/4x/gambc-v4_2_8/gsi'
../mkidirs /usr/pkg/bin
../install-sh -c -m 644 _gambcgsi.c /usr/pkg/lib//_gambcgsi.c
c++ -L/usr/lib -Wl,-R/usr/lib -Wl,-R/usr/pkg/lib -rdynamic -shared -o
libgambcgsi.so _gsilib.o _gambcgsi.o /usr/pkg/lib//libgambc.so -lutil
ld: cannot find -lgambc
gmake[1]: *** [install-post] Error 1
gmake[1]: Leaving directory
`/pkg_comp/obj/pkgsrc/lang/gambc/4x/gambc-v4_2_8/gsi'
gmake: *** [install-recursive] Error 1
*** Error code 2
Stop.
make: stopped in /usr/pkgsrc/lang/gambc
*** Error code 1
Stop.
During the earlier build phase, I do see objects being (seemingly
successfully) built, that do refer to -lgambc (which will be one built
in the work directories, not yet installed, I assume).
That is, the failure to find it does not seem to be related to any
failure to build it - this looks more like some kind of installation
process botch.
>Fix:
Home |
Main Index |
Thread Index |
Old Index