From owner-freebsd-ports@FreeBSD.ORG Fri Mar 9 23:04:48 2007 Return-Path: X-Original-To: freebsd-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 8CA5D16A404 for ; Fri, 9 Mar 2007 23:04:48 +0000 (UTC) (envelope-from eps@anna.ana.com) Received: from anna.ana.com (anna.ana.com [208.69.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA3513C46B for ; Fri, 9 Mar 2007 23:04:48 +0000 (UTC) (envelope-from eps@anna.ana.com) Received: from anna.ana.com (localhost [127.0.0.1]) by anna.ana.com (8.13.8/8.13.8) with ESMTP id l29Mr3vt029434 for ; Fri, 9 Mar 2007 14:53:04 -0800 (PST) Received: (from eps@localhost) by anna.ana.com (8.13.8/8.13.8/Submit) id l29Mr3Wp029433; Fri, 9 Mar 2007 14:53:03 -0800 (PST) Date: Fri, 9 Mar 2007 14:53:03 -0800 (PST) Message-Id: <200703092253.l29Mr3Wp029433@anna.ana.com> From: eps+pqry0703@ana.com (Eric P. Scott) To: freebsd-ports@freebsd.org Subject: Why are package builds failing for editors/abiword-plugins? 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: Fri, 09 Mar 2007 23:04:48 -0000 http://portsmon.freebsd.org/portoverview.py?category=editors&portname=abiword-plugins i386 and amd64 builds are "failing" as though something were forcing USE_AUTOTOOLS= libtool:15 and bypassing the included libtool. What's the difference? % ${WRKSRC}/libtool --features host: i386-portbld-freebsd6.2 enable shared libraries disable static libraries % ${LOCALBASE}/bin/libtool --features host: i386-portbld-freebsd6.2 enable shared libraries enable static libraries The latter builds extraneous .a files, which, of course, are picked up during the install phase. The package builder sees files that aren't in the PLIST (and aren't supposed to be), and it's reported as a failure. The included libtool is version 1.5.6, and the external libtool is version 1.5.22, so I can see how it might be beneficial to "enhance" the abiword-plugins port to work with either one. However, doing so merely to work around presumed misconfiguration on the build cluster doesn't strike me as appropriate. -=EPS=-