Date: Mon, 19 May 2003 15:20:52 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: ports-committers@freebsd.org Subject: Re: cvs commit: ports/devel/avr-libc Makefile Message-ID: <20030519222052.GA8210@rot13.obsecurity.org> In-Reply-To: <20030519235424.C21682@uriah.heep.sax.de> References: <20030519104604.GB17366@sunbay.com> <20030519125334.D2937@uriah.heep.sax.de> <20030519114332.GG17366@sunbay.com> <20030519115339.GI17366@sunbay.com> <20030519121239.GA6087@rot13.obsecurity.org> <20030519143325.H2937@uriah.heep.sax.de> <20030519153809.1b01f51b.Alexander@Leidinger.net> <20030519155824.M2937@uriah.heep.sax.de> <20030519213123.GG7480@rot13.obsecurity.org> <20030519235424.C21682@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 19, 2003 at 11:54:24PM +0200, Joerg Wunsch wrote: > As Kris Kennaway wrote: >=20 > > > > People which don't care about some few percent more performance > > > > don't need the default CPUTYPE, those who care will figure out how > > > > to do it. > > >=20 > > > That's exactly my point. > >=20 > > Joerg, can you please try and keep your bsd.cpu.mk axe-grinding > > separate from this discussion about the bug in your port? The place > > to discuss bsd.cpu.mk is in another thread. >=20 > Well, this was Alexander's comment... but anyway, no, bsd.cpu.mk is > exactly the problem. Without it poisoning the default CFLAGS, this > port worked/works fine. Setting CFLAGS is a supported, legal operation that is required to be supported by every other port in the collection. Ports that break when CFLAGS are broken, end of story. This brokenness was *revealed* by the recent bsd.cpu.mk commit, but as we've established it was there all along. It's now up to you, the port maintainer, to fix your ports so they conform to the standards of the ports collection. I hope I've now made this sufficiently clear that you can just fix the problem and we can both move on to more important things. Thanks, Kris --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+yVjEWry0BWjoQKURAjstAKDIrCPrzMJcNMXL8Hkotniy2n9G5wCgrNHy hdYUVX9LP6RoFr6iX2+jlyY= =bDZM -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519222052.GA8210>