From owner-freebsd-ports@FreeBSD.ORG Wed Feb 9 18:06:42 2005 Return-Path: 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 59B9616A4CE for ; Wed, 9 Feb 2005 18:06:42 +0000 (GMT) Received: from mailtest.sd73.bc.ca (mailtest.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E11F43D3F for ; Wed, 9 Feb 2005 18:06:42 +0000 (GMT) (envelope-from fcash-ml@sd73.bc.ca) Received: from localhost (localhost [127.0.0.1]) by mailtest.sd73.bc.ca (Postfix) with ESMTP id 771F1F1805; Wed, 9 Feb 2005 10:06:41 -0800 (PST) Received: from mailtest.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08514-01-83; Wed, 9 Feb 2005 10:06:40 -0800 (PST) Received: from s9.sbo (s9.sbo [192.168.0.9]) by mailtest.sd73.bc.ca (Postfix) with ESMTP id C0489F1804; Wed, 9 Feb 2005 10:06:40 -0800 (PST) From: Freddie Cash Organization: School District 73 - Kamloops, BC To: Paul Schmehl Date: Wed, 9 Feb 2005 10:06:39 -0800 User-Agent: KMail/1.7.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502091006.39787.fcash-ml@sd73.bc.ca> X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca cc: ports@freebsd.org Subject: Re: New port questions X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 18:06:42 -0000 On February 9, 2005 09:31 am, Paul Schmehl wrote: > I'm creating a new port - security/barnyard. I *thought* I had it > working right, and all of a sudden it's broken. Turns out some > changes have apparently been made to the configure.in script that > break the build. > See this webpage for the gory details: > > Here's my problem. Not only do I have to remove the two offending > lines in the configure.in file, which I should be able to do with sed > (haven't tested it yet though), or can I do this: "LDFLAGS-= -lz > -lssl"? Why not just create a patch file that removes those two lines, and stick that in the port's files/ directory. Then the port framework will do all the work for you. I've used this on the www/dansguardian ports without any problems. -- Freddie Cash, CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash-ml@sd73.bc.ca