Date: Wed, 17 Mar 2004 10:24:32 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/gcc34 Makefile Message-ID: <20040317182432.GA96023@dragon.nuxi.com> In-Reply-To: <20040317112344.GB86662@dragon.nuxi.com> References: <200403170818.i2H8IFYU008824@repoman.freebsd.org> <Pine.BSF.4.58.0403171036060.94079@acrux.dbai.tuwien.ac.at> <Pine.BSF.4.58.0403171135480.94079@acrux.dbai.tuwien.ac.at> <20040317112344.GB86662@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 17, 2004 at 03:23:44AM -0800, David O'Brien wrote: > On Wed, Mar 17, 2004 at 11:50:52AM +0100, Gerald Pfeifer wrote: > > 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. > > I *DID* test on i386 (5.2-CURRENT, full 'make world' just before testing > the port). I just re-tested on FreeBSD/i386: kieu(r):/usr/ports/lang/gcc34> /usr/bin/time -h make package ... Creating bzip'd tar ball in '/usr/ports/lang/gcc34/gcc-3.4.0_20040310.tbz' 49m57.11s real 16m21.78s user 7m13.72s sys kieu(r):/usr/ports/lang/gcc34> ll gcc-3.4.0_20040310.tbz -rw-r--r-- 1 root ncvs 13.0M Mar 17 09:48 gcc-3.4.0_20040310.tbz What breakage did you see? I didn't test on releng4, is that where the breakage occurred?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040317182432.GA96023>