Subject: how does devel/libgetopt/builtin.mk work?
To: None <firstname.lastname@example.org>
From: Jeremy C. Reed <email@example.com>
Date: 05/21/2004 18:42:41
Can someone explain how devel/libgetopt/builtin.mk works?
What should the correct behaviour do?
I don't need libgetopt. I am using glibc and I have a
When building psmisc I receive:
work.puget -> /scratch/pkgsrc/sysutils/psmisc/work.puget
===> Extracting for psmisc-20.1nb1
===> Required package libgetopt>=1.3: NOT found
libgetopt should not be required for me.
===> Verifying reinstall for ../../devel/libgetopt
===> libgetopt-1.3 is part of your Linux distribution
The above is from the Makefile; it is fine, but should never have got that
===> Returning to build of psmisc-20.1nb1
===> Required installed package patch>=2.2: patch-2.5.4nb2 found
===> Required installed package gcc3-c>=3.3.3: gcc3-c-3.3.3 found
===> Patching for psmisc-20.1nb1
===> Applying pkgsrc patches for psmisc-20.1nb1
===> Overriding tools for psmisc-20.1nb1
===> Buildlinking for psmisc-20.1nb1
getopt is not installed; can't buildlink files.
reed@puget:/usr/pkgsrc/sysutils/psmisc$ bmake show-var
reed@puget:/usr/pkgsrc/sysutils/psmisc$ bmake show-var PKG_PHASE=buildlink
The above should be "yes" I assume.
Jeremy C. Reed
BSD News, BSD tutorials, BSD links