Date: Mon, 21 Jan 2002 23:01:42 -0500 (EST) From: Mikhail Teterin <mi@aldan.algebra.com> To: will@csociety.org Cc: ports@FreeBSD.org Subject: Re: cvs commit: ports/graphics/gd2 Makefile pkg-plist ports/graphics/gd2/files Makefile.bsd Message-ID: <200201220401.g0M41jQ53644@aldan.algebra.com> In-Reply-To: <20020121222747.B18609@squall.waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[moved to -ports]
On 21 Jan, Will Andrews wrote:
> On Mon, Jan 21, 2002 at 10:19:06PM -0500, Mikhail Teterin wrote:
>> Well, the reason I did this is because some stuff, actually, just
>> expects to find gd.h -- not gd/gd.h (libwmf, for example, or gdtclft)
>> -- and needs to be patched somehow. Since all of the headers are
>> named gd<something>.h too, I think, it would be proper to install
>> them in include directly.
> You should have put this information in your commit log.
I thought I did... Oh, well.
> Regardless, such programs can easily -I${LOCALBASE}/include/gd,
> whereas programs that do gd/gd.h (which I believe is the standard way,
> if memory from playing around with gd from about 2-3 years ago
> serves) have a problem, unless you plan on symlinking gd to . in
> ${LOCALBASE/include.
That's a possibility -- depending on how many things break (most have
-I${LB}/inlude anyway). One way or the other things will need patching,
so -- I figured -- might do the right thing :-)
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201220401.g0M41jQ53644>