Date: Mon, 19 May 2003 11:16:49 +0200 From: Joerg Wunsch <j@uriah.heep.sax.de> To: Kris Kennaway <kris@obsecurity.org> Cc: ports-committers@FreeBSD.org Subject: Re: BROKEN tags (Re: cvs commit: ports/devel/avr-libc Makefile) Message-ID: <20030519111649.A2937@uriah.heep.sax.de> In-Reply-To: <20030519085637.GA71335@rot13.obsecurity.org>; from kris@obsecurity.org on Mon, May 19, 2003 at 01:56:38AM -0700 References: <200305190828.h4J8S8l0069634@repoman.freebsd.org> <20030519085637.GA71335@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
As Kris Kennaway wrote: > > Remove BROKEN. It's not that port that is broken, but FreeBSD 5.x in > > that it has broken /again/ all cross-compilation attempts. Whoever > > broke it ought to fix that. > > BROKEN indicates that the port does not compile. While I agree with > you that the fault lies with bsd.cpu.mk, this fact remains true. Still, by now, the policy has been that whoever broke the system is repsonsible for fixing it. If someone breaks buildworld, we don't mark the entire system `broken', but require him to fix the breakage. I'll file a formal request to -core for removal or at least deactivation by default of bsd.cpu.mk anyway. I'm sick of the breakage it caused, FreeBSD 5.x is the only known Unix that breaks cross-compilation builds in that way. In contrast, it basically gains nothing (MHO), the possible gain it could get can as well be achieved by requiring the user to edit their CFLAGS line in /etc/make.conf, as opposed to requiring them to edit their CPUTYPE line in the same file. It'll only take me another night to write down the reasoning for that application. > ... If > it's not there, then they will encounter confusing compilation > failures when they go to build the port, and among other things this > looks bad for FreeBSD. That's exactly why i think that bsd.cpu.mk needs to go away. It looks bad for FreeBSD. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519111649.A2937>