From owner-freebsd-pkg@FreeBSD.ORG Wed Apr 8 19:02:49 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22A64949 for ; Wed, 8 Apr 2015 19:02:49 +0000 (UTC) Received: from list.sco.com (list.sco.com [69.36.163.214]) by mx1.freebsd.org (Postfix) with SMTP id D9CD3978 for ; Wed, 8 Apr 2015 19:02:48 +0000 (UTC) Received: (qmail 16275 invoked from network); 8 Apr 2015 19:02:41 -0000 Received: from nimbus.nj.sco.com (69.36.163.214) by tasmania.ut.sco.com with SMTP; 8 Apr 2015 19:02:41 -0000 Received: from [127.0.0.1] (host10.nj.vpn.unxisco.com [10.147.73.10]) by nimbus.nj.sco.com (8.12.9/UW7.1.3) with ESMTP id t38J2eHH012422; Wed, 8 Apr 2015 15:02:41 -0400 (EDT) Message-ID: <55257B54.4050700@xinuos.com> Date: Wed, 08 Apr 2015 15:02:44 -0400 From: John Wolfe User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-pkg@freebsd.org Subject: Use of pkg plugins breaks the build of /usr/ports software Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2015 19:02:49 -0000 Having built a pkg-plugin based on the pkg-plugin-template at https://github.com/freebsd/pkg-plugins and adding > PLUGINS [ > "x-adminsync", > ] the plugin is working as desired. Good so far...... I was caught off guard when later attempting to "make" something in /usr/ports. The builds fail miserably with multiple > pkg-static: Loading of plugin 'x-adminsync' failed: Service unavailable > pkg-static: Plugins cannot be loaded > make[1]: "/usr/ports/Mk/bsd.port.mk" line 1206: warning: > "/usr/local/sbin/pkg-static version -t 1.4.12 1.3.8" returned non-zero > status I would not expect that a static binary be able to load and use a relocatable object so I am surprised that it even tried to do so. Even so, a failure should be expected and not terminate the pkg-static process. Is this a bug, works as designed? -- John Wolfe Xinuos, Inc.