Date: Mon, 12 Feb 2007 17:01:45 -0800 From: Chuck Swiger <cswiger@mac.com> To: Andrew Pantyukhin <infofarmer@FreeBSD.org> Cc: youshi10@u.washington.edu, freebsd-ports@freebsd.org, Tom McLaughlin <tmclaugh@freebsd.org> Subject: Re: Porting a Linux application to FreeBSD Message-ID: <B7AEAD75-598D-4A35-BCE5-CC32EC1056CB@mac.com> In-Reply-To: <cb5206420702121639xe11882atc7a37b2125256400@mail.gmail.com> References: <Pine.LNX.4.43.0702121435340.10676@hymn08.u.washington.edu> <1171323867.21134.1.camel@localhost> <cb5206420702121639xe11882atc7a37b2125256400@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 12, 2007, at 4:39 PM, Andrew Pantyukhin wrote:
>> Linux does not have it's own libpng and neither do we. Most Linux
>> distros and us use libpng from libpng.org. I took a quick look at
>> the
>> current libpng in the ports tree and it appears to have
>> png_read_png().
>> With out seeing a Makefile for the ports system and some error
>> output it
>> is hard to comment as to the specific reason stuff is failing for
>> you.
>
> Yes, but my money says
> ==
> =CPPFLAGS= -I${LOCALBASE}/include
> =LDFLAGS= -L${LOCALBASE}/lib
> =GNU_CONFIGURE= yes
> =CONFIGURE_ENV= CPPFLAGS="${CPPFLAGS}" LDFLAGS="${LDFLAGS}"
> ===
> will help, it always(x0.999) does :-) It's one
> of those things everyone knows about but no one
> commits into Mk/* because we enjoy routine so
> much.
I believe your suggestion is exactly right as to the problem; my only
question would be whether it would be better to change the ports Mk
infrastructure, or to change the system compiler to add /usr/local/
{include,lib} to the default search paths...
--
-Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B7AEAD75-598D-4A35-BCE5-CC32EC1056CB>