From owner-freebsd-ports@FreeBSD.ORG Sat Dec 3 05:18:45 2005 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 AA63E16A41F for ; Sat, 3 Dec 2005 05:18:45 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42B2E43D5D for ; Sat, 3 Dec 2005 05:18:45 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id jB35Ifv1032638; Sat, 3 Dec 2005 00:18:42 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <20051203001127.GA3532@night.dbn> References: <20051129192509.GA54936@night.dbn> <20051129204003.GA56311@xor.obsecurity.org> <20051203001127.GA3532@night.dbn> Date: Sat, 3 Dec 2005 00:18:39 -0500 To: Diane Bruce From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.4 Cc: freebsd-ports@freebsd.org Subject: Re: Just a note about include files in ports 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: Sat, 03 Dec 2005 05:18:45 -0000 At 7:11 PM -0500 12/2/05, Diane Bruce wrote: >On Tue, Nov 29, 2005 at 03:40:03PM -0500, Kris Kennaway wrote: >> On Tue, Nov 29, 2005 at 02:25:09PM -0500, Diane Bruce wrote: >> > Hi, >> > > > > Be careful with includes in a port build. I have caught two > > > ports using the include files installed by a previous version >... > > > can break or at least compile incorrectly if the port include > > > files change between releases. If you are lucky, it will fail. > > >Seeing as Pav and others have refuted the KDE and GNOME include >theory, I guess it is not a huge problem after all, since no one >else has commented. ;-) Actually, the bash port has tripped over this a few times, when it is using a different version of readline than the one in the base system. In that case it was not tripping over the previous install of the port, but tripping over a conflict between the base system and the version the port wanted to use. And as it happens, I tripped over something similar in a program of my own (not a port), which I've been building for years. In some situations it would build with one version of an include file (one it had), and then link with the library from the base system (instead of the one the program builds for itself). And I tripped over that on the Sunday before Diane sent the message that started this thread! I'm sure this had caused errors for me with my own program in the past, but this is the first time that I noticed what the problem really was. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu