From owner-freebsd-ports@FreeBSD.ORG Sun Nov 12 20:50:48 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEFAB16A415 for ; Sun, 12 Nov 2006 20:50:48 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3345143D79 for ; Sun, 12 Nov 2006 20:50:48 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 185661A3C19; Sun, 12 Nov 2006 12:50:48 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9A4B951361; Sun, 12 Nov 2006 15:50:37 -0500 (EST) Date: Sun, 12 Nov 2006 15:50:37 -0500 From: Kris Kennaway To: Stefan Sperling Message-ID: <20061112205037.GA19842@xor.obsecurity.org> References: <20061112185901.GA92932@ted.stsp.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <20061112185901.GA92932@ted.stsp.lan> User-Agent: Mutt/1.4.2.2i Cc: freebsd-ports@freebsd.org Subject: Re: How can I deal with build-time port conflicts? 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: Sun, 12 Nov 2006 20:50:48 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 12, 2006 at 07:59:01PM +0100, Stefan Sperling wrote: > Hello, >=20 > I am updating audio/beast to version 0.7.0. >=20 > At first it didn't seem to work, it was segfaulting like crazy when run. > With the friendly help of upstream developers I was able > to track this down to a shared library problem. >=20 > The port sets LDFLAGS=3D"-L/usr/local/lib" in the environment of the > configure script, because otherwise the configure script fails to > find required libraries, like libmad, for example. >=20 > It seems that this causes the beast-0.7.0 binaries to be linked > with beast-0.6.x libraries installed in /usr/local/lib. > Deinstalling beast-0.6.x before compiling 0.7.0 solves the issue, > the application runs just fine. So a clean upgrade requires > the previous version of the port to be removed *before* the new > version is built. >=20 > Is there any way I can make sure that the previous version of the port > is not installed while building the new version? I've tried setting > CONFLICTS to beast-[0-6]*, but CONFLICTS is not checked until install > time. I need the check to be performed before anything else. >=20 > Or is the rather ugly LDFLAGS hack to blame, i.e. should I try to find > a better way to make configure pick up required libraries? The better way is to fix the port build to not pick up the wrong libraries, i.e. by using -L. -L${LOCALBASE}/lib to pick up the local versions first. Note also that you shouldn't be using /usr/local/lib. Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFV4kdWry0BWjoQKURAkw4AKDboUldMR44U/zvZjuFeGHFsm/MZwCgrulr HLOpoVRWwsWnVKIst+diijU= =vyrw -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--