From owner-freebsd-ports@FreeBSD.ORG Thu Jun 14 20:03:11 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F15816A4A7 for ; Thu, 14 Jun 2007 20:03:11 +0000 (UTC) (envelope-from bkelly@vadev.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4089213C465 for ; Thu, 14 Jun 2007 20:03:11 +0000 (UTC) (envelope-from bkelly@vadev.org) Received: (qmail 26502 invoked from network); 14 Jun 2007 19:36:31 -0000 Received: from vadev.org (HELO [192.168.1.84]) (Desdicardo@[66.92.166.151]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 14 Jun 2007 19:36:31 -0000 Message-ID: <467198BD.9020401@vadev.org> Date: Thu, 14 Jun 2007 15:36:29 -0400 From: Ben Kelly User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: install-ldconfig-file target problem X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2007 20:03:11 -0000 Hello, For the last few months I have been receiving odd messages from my system when I try to use portupgrade -p on certain ports. Specifically, the package fails to be created do to a (null) prefix entry on certain files. This problem also shows up when deinstalling a package. For example: vir# pwd /usr/ports/ports-mgmt/portupgrade vir# make deinstall ===> Deinstalling for ports-mgmt/portupgrade ===> Deinstalling portupgrade-2.2.6_3,2 pkg_delete: file '(null)/libdata/ldconfig/portupgrade' doesn't really exist pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) vir# I believe this was being caused by the @cwd command being placed on a separate line from its argument in the .PLIST.mktmp file. For example: vir# pwd /var/tmp/ports/usr/ports/ports-mgmt/portupgrade/work vir# tail -3 .PLIST.mktmp @unexec /sbin/ldconfig -R @cwd libdata/ldconfig/portupgrade vir# I am running: FreeBSD vir.in.vadev.org 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jun 13 17:20:53 EDT 2007 root@vir.in.vadev.org:/usr/obj/usr/src/sys/SERVER i386 My ports tree was portsnap'd just before the uname build time. My src tree was updated perhaps 12 hours earlier. I was able to fix the problem locally with the following patch: --- bsd.port.mk.orig Thu Jun 14 15:09:35 2007 +++ bsd.port.mk.new Thu Jun 14 15:10:51 2007 @@ -4008,7 +4008,7 @@ .endif @${ECHO_CMD} ${USE_LDCONFIG} | ${TR} ' ' '\n' \ > ${PREFIX}/${LDCONFIG_DIR}/${UNIQUENAME} - @${ECHO_CMD} "@cwd" >> ${TMPPLIST} + @${ECHO_CMD} -n "@cwd " >> ${TMPPLIST} @${ECHO_CMD} ${LDCONFIG_DIR}/${UNIQUENAME} >> ${TMPPLIST} .if defined(NO_LDCONFIG_MTREE) @${ECHO_CMD} "@unexec rmdir ${LDCONFIG_DIR} >/dev/null 2>&1 || true" >> ${TMPPLIST} Is this the correct fix or is there something else wrong with my configuration? Thanks. - Ben