graphics/png does not build with lang/gcc
bf1783 at googlemail.com
Thu Mar 8 04:59:11 UTC 2012
On 3/8/12, Mark Linimon <linimon at lonesome.com> wrote:
> On Wed, Mar 07, 2012 at 12:11:52PM +0000, b. f. wrote:
>> The custom gcc article that you are attempting to use was written at
>> a time when some of the related port Makefiles had some shortcomings
>> that no longer exist, and is not the recommended way to use lang/gcc*
>> for ports.
> Would you be interested in helping to update it?
If you like, I can suggest a few changes. But I thought that it was
primarily Martin's article, which he wrote when he was benchmarking
perl with different toolchains.
>> For all but a handful of ports that lang/gcc* depends upon, or
>> those that don't respect the toolchain-related variables, you can just
>> install lang/gcc or lang/gcc46 and set USE_GCC=4.6 in your build
>> environment, an included Makefile, or on the command line.
> Setting USE_* in e.g. /etc/make.conf is always incorrect, see:
> You can wind up in the degenerate case maknig gcc46 depend upon itself.
That is why I wrote: "... all but a handful of ports that lang/gcc*
depends upon ...".
The OP wanted to find a way to use lang/gcc* in a custom build of a
port -- which, as you know from your own work, isn't well-supported in
Ports right now. (We make an attempt to be flexible, and there is some
infrastructure to do so, but many ports aren't tested with different
toolchains. Some tinkering is inevitably involved if any substantial
number of ports are built in this way.) The OP was willing to use
invasive changes suggested by the custom gcc article. Therefore, I
assumed that he wasn't interested in strictly adhering to our
guidelines, and just wanted a pragmatic solution, which is what I
offered to him. Setting USE_GCC in this case is safer and easier than
what he was doing. I didn't intend to suggest that anyone make
unqualified use of it in make.conf. There is already far too much
abuse of that special file.
More information about the freebsd-ports