Dara Hazeghi wrote:

Hmm... So there's no 'finkrc' where I can set global
settings? With MAKEFLAGS it may be merely irritating,
but for instance, I'd like to override CC to avoid
having to symlink /sw/bin/gcc to /sw/bin/distcc.

I agree that cleaning up certainly helps debugging.
But I think that it'd be far cleaner for things like
CC to have a file for settings them. For instance
ccache-default strikes me as something of a hack.

Depends on your perspective. For one thing, ccache was designed to be symlinked to gcc et al, so it could be transparently implemented. For another, we are not gentoo, where the way you build and optimize things is infinitely tweakable. One of the goals of fink's packaging system is for the resultant .deb file to be the same no matter what system it's built on. With some exceptions, we do exactly that, and it's for those reasons that the environment gets scrubbed before building.

I've been personally using distcc with fink for some time, but as a project admin, I also have the ability to go and update packages that don't build so that they get -j1 forced when building. Having an official stance of supporting it, however, is another matter.

This is not an issue of technical possibility, it would be very easy to write a finkrc system. However, that is contrary to the "deb binary portability" part of fink's charter, if you will. Heck, on Mac OS X, I'd hazard to say that other than distcc, you really don't get much out of customizing flags anyways, because Apple's gcc has traditionally been pretty buggy for optimizations above -O or -Os (there are exceptions, of course).

Before going any further on this thread, I suggest you go read some of the archives; this is a topic that's been hashed and re-hashed many times.

--
Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/
gpg: 6401 D02A A35F 55E9 D7DD  71C5 52EF A366 D3F6 65FE
We put a lot of thought into our defaults.  We like them.  If we
didn't, we would have made something else be the default.  So keep
your cotton-pickin' hands off our defaults.  Don't touch.  Consider
them mandatory.  "Mandatory defaults" has a nice ring to it.


Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to