Date: Mon, 31 Jan 2005 10:03:59 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Pav Lucistnik <pav@FreeBSD.org> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/mozart Makefile Message-ID: <20050131100359.GA98611@FreeBSD.org> In-Reply-To: <200501292340.j0TNe7eq054403@repoman.freebsd.org> References: <200501292340.j0TNe7eq054403@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 29, 2005 at 11:40:07PM +0000, Pav Lucistnik wrote: > pav 2005-01-29 23:40:07 UTC > > FreeBSD ports repository > > Modified files: > lang/mozart Makefile > Log: > - Fix build on FreeBSD 5 > gcc 3.x makes new assumptions on private c++ data > gcc 2.95 compiles mozart with no problems Actually, I tend to avoid "fixes" like this (workarounds really). Since 2.95 is obviously going to be supported less and less in the future, and we're officially done with 4.X-RELEASEs, we should probably refrain from pulling in compiler that is older than what's in the base now. Forcing GCC to 2.95 should only be used in extreme cases, which cannot be solved by simple patching. For this very case, I don't want to test it and fix myself since this port want emacs and stuff, and I do not want to pollute my working system with this, but since submitter states that the problem with newer GCC is because it "makes new assumptions on private C++ data", I'd rather see a patch committed, or some reasoning why it cannot be. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050131100359.GA98611>