Date: Wed, 17 Mar 2004 11:50:52 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: "David E. O'Brien" <obrien@FreeBSD.org> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/gcc34 Makefile Message-ID: <Pine.BSF.4.58.0403171135480.94079@acrux.dbai.tuwien.ac.at> In-Reply-To: <Pine.BSF.4.58.0403171036060.94079@acrux.dbai.tuwien.ac.at> References: <200403170818.i2H8IFYU008824@repoman.freebsd.org> <Pine.BSF.4.58.0403171036060.94079@acrux.dbai.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Mar 2004, Gerald Pfeifer wrote: > I did something similar to the gcc33 port over the weekend, but during > my tests (on i386, for example) I still had to hardcode CONFIGURE_TARGET, > though gcc34 builds just fine with your more minimal approach. > > Do you have any idea why that might be? I'm afraid I know. Your commit apparently broke the port an all platforms but amd64. :-( Have you tested this following the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-testing.html ? For invasive changes like this, I'd like to ask you to always test at least i386 when committing changes to ports that I maintain. Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.58.0403171135480.94079>