From owner-freebsd-current@FreeBSD.ORG Thu Aug 18 20:59:27 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FDDC16A41F for ; Thu, 18 Aug 2005 20:59:27 +0000 (GMT) (envelope-from stefan@fafoe.narf.at) Received: from viefep11-int.chello.at (viefep11-int.chello.at [213.46.255.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FC1343D49 for ; Thu, 18 Aug 2005 20:59:25 +0000 (GMT) (envelope-from stefan@fafoe.narf.at) Received: from wombat.fafoe.narf.at ([213.47.85.26]) by viefep11-int.chello.at (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050818205923.RIWF2678.viefep11-int.chello.at@wombat.fafoe.narf.at>; Thu, 18 Aug 2005 22:59:23 +0200 Received: by wombat.fafoe.narf.at (Postfix, from userid 1001) id DB201F6; Thu, 18 Aug 2005 22:59:22 +0200 (CEST) Date: Thu, 18 Aug 2005 22:59:22 +0200 From: Stefan Farfeleder To: Phil Oleson Message-ID: <20050818205921.GR21905@wombat.fafoe.narf.at> Mail-Followup-To: Phil Oleson , current@freebsd.org References: <20050818165050.58B835D07@ptavv.es.net> <4304DAE0.1040702@nixil.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4304DAE0.1040702@nixil.net> User-Agent: Mutt/1.5.9i Cc: current@freebsd.org Subject: Re: Unable to build libedit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2005 20:59:27 -0000 On Thu, Aug 18, 2005 at 01:00:48PM -0600, Phil Oleson wrote: > > Personally, I'm still unsure why we have histedit.h pre-installed in > src/include. This might be showing my ignorance of some of the build > mechanisms in the main src tree, but wouldn't this work out better if > histedit.h was located in src/lib/libedit until install time? I guess the reason for putting most headers into src/include is that it prevents dozens of -I paths while building. Stefan