From owner-freebsd-ports@FreeBSD.ORG  Tue Mar 20 19:16:20 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6661216A400
	for <freebsd-ports@freebsd.org>; Tue, 20 Mar 2007 19:16:20 +0000 (UTC)
	(envelope-from ale@FreeBSD.org)
Received: from lab.alexdupre.com (lab.alexdupre.com [81.174.31.42])
	by mx1.freebsd.org (Postfix) with ESMTP id F32DD13C448
	for <freebsd-ports@freebsd.org>; Tue, 20 Mar 2007 19:16:19 +0000 (UTC)
	(envelope-from ale@FreeBSD.org)
Received: (qmail 58396 invoked from network); 20 Mar 2007 19:16:18 -0000
Received: from unknown (HELO ?192.168.178.2?) (192.168.178.2)
	by lab.alexdupre.com with SMTP; 20 Mar 2007 19:16:18 -0000
Message-ID: <46003302.1040908@FreeBSD.org>
Date: Tue, 20 Mar 2007 20:16:18 +0100
From: Alex Dupre <ale@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.10 (X11/20070310)
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
References: <20070320182602.GA71050@icarus.home.lan>
In-Reply-To: <20070320182602.GA71050@icarus.home.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: lang/php5 - duplicate script for target
	"main/internal_functions.lo"
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2007 19:16:20 -0000

Jeremy Chadwick wrote:
> Anyone make heads or tails of the warning?

Simply gnore it, or come up with a patch that eliminates it.

--
Alex Dupre