Subject: use of bsd.lib.mk in pkgsrc
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 05/19/2002 14:09:44
a number of pkgs currently use bsd.lib.mk in pkgsrc for building
libraries. While this is nice, its resulting in broken PLISTs and in some
cases, broken packages. The basic reason is that the set of libraries
produced varies by MACHINE_ARCH. For example, on mipsel (pmax),
everything is PIC so there isn't a seperate libfoo_pic.a created. Thus a
PLIST generated on i386 may list libfoo_pic.a and the PLIST will be wrong
on pmax. Also, I've come across some pkgs which rather than using the
install target from bsd.lib.mk, they explicitly add the install commands.
Now, they end up trying to install a libfoo_pic.a which doesn't exist and
the install fails.
Since there are around 15 pkgs that get patched to use bsd.lib.mk (and an
unknown number which might already use it), I wonder if we need a slightly
more unified way of handling this. Maybe a BSD_LIBS variable which would
expand into the PLIST? Or maybe some flags in the PLIST which would get
turned into @comments on arch's which don't install the particular flavor
of lib? Something like:
Any other suggestions?
I'd like to fix this asap as it breaks several pkgs on mips.