On 2009-11-07 22:06:36, Mark Linimon wrote: > > There were several more working, but a recent compiler update broke them. > At that time the portmgr team went ahead and marked the ports "broken". > That both advises users that they don't compile, and also triggers a > periodic email to the ports@ mailing list. Beyond that we have to rely > on work done by individual contributors.
Seems reasonable. > Most of the general mechanisms for selecting "port alternative foo vs. > bar" live in ports/Mk. In particular, you will probably want to look at > ports/Mk/bsd.gcc.mk. A more advanced example is in bsd.java.mk. Note: > don't feel bad if you don't understand the contents of these files; they > have evolved to their current state over quite some period of time. It's > perfectly fair to ask for help. It's on the list. Thanks! > For something like this that isn't widely used, I wouldn't spend too much > time on anything other than i386 and amd64. That's where the majority of > our user base is (I'm guessing 80% and 15%, respectively, based on the PR > arrival statistics.) That's good to know. I don't have any sparc64 machines laying around... M
pgpAXccXnvBs2.pgp
Description: PGP signature
