Subject: Re: security/pam-ldap is broken??
To: None <segv@netctl.net>
From: Jeremy C. Reed <reed@reedmedia.net>
List: tech-pkg
Date: 12/02/2005 11:32:19
On Fri, 2 Dec 2005 segv@netctl.net wrote:
> "../../mk/wrapper/../../mk/buildlink3/../../mk/wrapper/../../mk/buildlink3/bsd.buildlink3.mk"
> line 325: warning: Couldn't read shell's output for "/opt/pkg/sbin/pkg_info
> -K . -qp | /opt/pkg/bin/nbsed -e "s,^[^/]*,,;q""
Notice that the -qp is not followed by the needed argument. The pkgsrc
framework should not run the command if the variable is empty.
(I copied that verbatim from an earlier email I wrote.)
I believe this is caused because pkgsrc detected that you have a package
provided file but then no package was actually providing it.
This is somewhere in mk/pam.buildlink3.mk or
databases/openldap/buildlink3.mk I believe.
This has happened to me several times, because I use Linux systems where
everyone component is provided my my pkgsrc ... but I didn't provide a
buildlink3.mk file for my pkgsrc's glibc for example.
I added this patch just to give me some diagnostics:
Index: mk/buildlink3/bsd.buildlink3.mk
===================================================================
RCS file: /cvsroot/pkgsrc/mk/buildlink3/bsd.buildlink3.mk,v
retrieving revision 1.171
diff -b -u -r1.171 bsd.buildlink3.mk
--- mk/buildlink3/bsd.buildlink3.mk 1 Jun 2005 18:03:06 -0000 1.171
+++ mk/buildlink3/bsd.buildlink3.mk 2 Dec 2005 19:29:28 -0000
@@ -322,7 +322,7 @@
. else
. if empty(BUILDLINK_PKGNAME.${_pkg_}:M*not_found)
BUILDLINK_PREFIX.${_pkg_}!= \
- ${_BLNK_PKG_INFO.${_pkg_}} -qp ${BUILDLINK_PKGNAME.${_pkg_}} | ${SED} -e "s,^[^/]*,,;q"
+ ${_BLNK_PKG_INFO.${_pkg_}} -qp ${BUILDLINK_PKGNAME.${_pkg_}} | ${SED} -e "s,^[^/]*,,;q" -e "s,xxx"${_pkg_}",jcr,"
. else
BUILDLINK_PREFIX.${_pkg_}= BUILDLINK_PREFIX.${_pkg_}_not_found
. endif
Then you will get same error message but now it will show the "xxx" and
the package name with the problem and my initials. (This patch is no fix.
It just helps to find missing buildlink3.mk file. It has been a while
since I have looked at this.)
Let us know what you find.
Jeremy C. Reed
BSD News, BSD tutorials, BSD links
http://www.bsdnewsletter.com/