Date: Tue, 29 Nov 2005 15:40:03 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Diane Bruce <db@db.net> Cc: freebsd-ports@freebsd.org Subject: Re: Just a note about include files in ports Message-ID: <20051129204003.GA56311@xor.obsecurity.org> In-Reply-To: <20051129192509.GA54936@night.dbn> References: <20051129192509.GA54936@night.dbn>
next in thread | previous in thread | raw e-mail | index | archive | help
--ew6BAiZeqk4r7MaW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Nov 29, 2005 at 02:25:09PM -0500, Diane Bruce wrote:
> Hi,
>=20
> Be careful with includes in a port build. I have caught two ports using
> the include files installed by a previous version of the port instead
> of the local port copy of the same include file. (Yes, one was in one
> of my own ports.) In particular, configure args that put the -I
> to /usr/local/include or /usr/X11/include before the -I ${WRKSRC}/..../in=
clude
> can break or at least compile incorrectly if the port include files change
> between releases. If you are lucky, it will fail.
Parts of KDE and GNOME do this :-( It's one of the main reasons that
'portupgrade' doesn't just work for upgrading them.
Kris
--ew6BAiZeqk4r7MaW
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
iD8DBQFDjLyjWry0BWjoQKURAoAcAKDM93a/A8I5QXt1WRAeR6n0XOaIygCfVLVA
eyKq73OKa8zk17CozS4ySZw=
=vUCi
-----END PGP SIGNATURE-----
--ew6BAiZeqk4r7MaW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051129204003.GA56311>