From owner-freebsd-ports@FreeBSD.ORG Tue May 23 00:35:39 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 5268316ACB5 for ; Tue, 23 May 2006 00:35:39 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx1.parodius.com (mx1.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFF8943D72 for ; Tue, 23 May 2006 00:35:34 +0000 (GMT) (envelope-from jdc@parodius.com) Received: by mx1.parodius.com (Postfix, from userid 500) id 970125E11; Mon, 22 May 2006 17:35:34 -0700 (PDT) Date: Mon, 22 May 2006 17:35:34 -0700 From: Jeremy Chadwick To: freebsd-ports@freebsd.org Message-ID: <20060523003534.GA78532@pentarou.parodius.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <200605221543.02228.beech@alaskaparadise.com> <20060523000810.GA77461@pentarou.parodius.com> <200605221630.38308.beech@alaskaparadise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605221630.38308.beech@alaskaparadise.com> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.11 Subject: Re: Help with configure.in 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: Tue, 23 May 2006 00:35:40 -0000 On Mon, May 22, 2006 at 04:30:36PM -0800, Beech Rintoul wrote: > I'm not sure how to add that into the makefile. Autoconf needs to be called > after configure.in is patched. With the stock configure.in autoconf doesn't > get called as above it just goes straight into the build. The porter's > Handbook wasn't a lot of help. Have you tried looking through /usr/ports/Mk/* ? Something like `grep -ri autoconf /usr/ports/Mk` should point you to some comments and general stuff. Also try looking at other ports that use some of those variables (`grep -r {variable} /usr/ports`). We have some framework for autoconf handling in there already. I've never used it (I usually rely on pre-built configure scripts, rather than build them during build-time), but it looks pretty robust. Others here should be able to help; sorry I can't be of much more... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |