Date: Sun, 12 Nov 2006 19:59:01 +0100 From: Stefan Sperling <stsp@stsp.in-berlin.de> To: freebsd-ports@freebsd.org Subject: How can I deal with build-time port conflicts? Message-ID: <20061112185901.GA92932@ted.stsp.lan>
next in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I am updating audio/beast to version 0.7.0. 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. 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. 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. 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. 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? Thanks, --=20 stefan http://stsp.in-berlin.de PGP Key: 0xF59D25F0 --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFV2715dMCc/WdJfARAgQFAJ0XQ+hnA9TpJp0Y6i5q8tR4V9wrmACgqSOu /OWuxeyuXkRsnAco/Uqy11g= =drYo -----END PGP SIGNATURE----- --DocE+STaALJfprDB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061112185901.GA92932>