From owner-freebsd-ports Sun Mar 24 12:39:37 2002 Delivered-To: freebsd-ports@freebsd.org Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.8.210.226]) by hub.freebsd.org (Postfix) with ESMTP id 08E3D37B400 for ; Sun, 24 Mar 2002 12:39:34 -0800 (PST) Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id g2OKdYX15519; Sun, 24 Mar 2002 15:39:34 -0500 (EST) (envelope-from alane) Date: Sun, 24 Mar 2002 15:39:33 -0500 From: Alan Eldridge To: Miguel Mendez Cc: freebsd-ports@FreeBSD.ORG Subject: Re: ports/36254: Conflicting function definition with standard libraries Message-ID: <20020324203933.GB64705@wwweasel.geeksrus.net> References: <200203241620.g2OGK3X69485@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200203241620.g2OGK3X69485@freefall.freebsd.org> User-Agent: Mutt/1.3.28i X-message-flag: Magic 8-Ball says "Outlook not so good." I'll ask it about Exchange next. Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Mar 24, 2002 at 08:20:03AM -0800, Miguel Mendez wrote: >The following reply was made to PR ports/36254; it has been noted by GNATS. > > Unfortunately, that will break compilation of the port on older systems, > where that function it's not part of libc. My humble suggestion: > > Then, patch the source code and surround that function with and #ifdef > NEED_STRNSTR Nope. 1. Internal libwww should not be built, so no need to patch. 2. If it were being used, function doesn't match system function, so can't remove, must rename and patch all calls to it that fail. -- AlanE "When the going gets weird, the weird turn pro." - HST To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message