cvs commit: ports/lang/gcc34 Makefile
David O'Brien
obrien at FreeBSD.org
Wed Mar 17 10:24:39 PST 2004
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?
More information about the cvs-ports
mailing list