Re: RELENG_8 buildworld broken?

2009-12-09 Thread Chris H
On Wed, December 9, 2009 3:33 pm, Pieter de Goeje wrote: > On Wednesday 09 December 2009 23:14:13 ocean wrote: > >> Pieter de Goeje wrote: >> >>> Actually, the way you specified CFLAGS overrides CPUTYPE. AFAIK you >>> should set CFLAGS/CPUTYPE like this: CPUTYPE?= >>> CFLAGS+=... >>> >>> >>> Th

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Pieter de Goeje
On Wednesday 09 December 2009 23:14:13 ocean wrote: > Pieter de Goeje wrote: > > Actually, the way you specified CFLAGS overrides CPUTYPE. AFAIK you > > should set CFLAGS/CPUTYPE like this: > > CPUTYPE?= > > CFLAGS+=... > > > > Though bothering with CPUTYPE or CFLAGS is actually a waste of time

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Ben Morrow
Quoth Roland Smith : > On Wed, Dec 09, 2009 at 01:09:12PM -0800, Jeremy Chadwick wrote: > > > Basically, all this comes back to the same thing: the entire "base > > system" concept needs to be revisited (that's a nice way of saying > > "nuked from orbit", but that's my opinion). > > Hmm, I kind

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Roland Smith
On Wed, Dec 09, 2009 at 01:09:12PM -0800, Jeremy Chadwick wrote: > The problem is this: > > - User installs OS > - User creates src.conf with numerous WITHOUT_xxx entries. Examples: > > WITHOUT_ATM=true > WITHOUT_SENDMAIL=true > > - User is forced to go through above said directories and cro

Re: RELENG_8 buildworld broken?

2009-12-09 Thread ocean
Pieter de Goeje wrote: Actually, the way you specified CFLAGS overrides CPUTYPE. AFAIK you should set CFLAGS/CPUTYPE like this: CPUTYPE?= CFLAGS+=... Though bothering with CPUTYPE or CFLAGS is actually a waste of time if you ask me. I've never observed any measurable improvement in the spe

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Jeremy Chadwick
On Wed, Dec 09, 2009 at 08:55:20PM +0100, Pieter de Goeje wrote: > On Wednesday 09 December 2009 20:32:39 Kevin Oberman wrote: > > > Date: Wed, 09 Dec 2009 17:36:26 +0100 > > > From: ocean > > > Sender: owner-freebsd-sta...@freebsd.org > > > > > These options are not useless. You can for instance

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Pieter de Goeje
On Wednesday 09 December 2009 20:32:39 Kevin Oberman wrote: > > Date: Wed, 09 Dec 2009 17:36:26 +0100 > > From: ocean > > Sender: owner-freebsd-sta...@freebsd.org > > > > Pieter de Goeje wrote: > > > The problem only occurs when doing a parallel make world (make -j8 > > > buildworld). In the past

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Kevin Oberman
> Date: Wed, 09 Dec 2009 17:36:26 +0100 > From: ocean > Sender: owner-freebsd-sta...@freebsd.org > > Pieter de Goeje wrote: > > > > The problem only occurs when doing a parallel make world (make -j8 > > buildworld). In the past I have always successfully built world using -j4. > > I > > guess

Re: RELENG_8 buildworld broken?

2009-12-09 Thread ocean
Pieter de Goeje wrote: The problem only occurs when doing a parallel make world (make -j8 buildworld). In the past I have always successfully built world using -j4. I guess the recent upgrade of this machine from dual core to quad core just made the problem visible. - Pieter __

Re: RELENG_8 buildworld broken?

2009-12-09 Thread Pieter de Goeje
On Wednesday 09 December 2009 01:50:03 Pieter de Goeje wrote: > I've blown away /usr/obj, checked out a fresh source tree, but no luck: > > cc -O2 -pipe -DHAVE_GTHR_DEFAULT -DIN_GCC -DIN_TARGET_LIBS -I. > -I/data/FreeBSD/FreeBSD-8.x/src/gnu/lib/libobjc/../../usr.bin/cc/cc_tools > -I/data/FreeBSD/F

RELENG_8 buildworld broken?

2009-12-08 Thread Pieter de Goeje
I've blown away /usr/obj, checked out a fresh source tree, but no luck: cc -O2 -pipe -DHAVE_GTHR_DEFAULT -DIN_GCC -DIN_TARGET_LIBS -I. -I/data/FreeBSD/FreeBSD-8.x/src/gnu/lib/libobjc/../../usr.bin/cc/cc_tools -I/data/FreeBSD/FreeBSD-8.x/src/gnu/lib/libobjc/../../../contrib/libobjc/objc -I/data