From owner-freebsd-current Tue Jun 9 23:12:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03198 for freebsd-current-outgoing; Tue, 9 Jun 1998 23:12:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03042 for ; Tue, 9 Jun 1998 23:11:18 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA26711; Wed, 10 Jun 1998 16:11:05 +1000 Date: Wed, 10 Jun 1998 16:11:05 +1000 From: Bruce Evans Message-Id: <199806100611.QAA26711@godzilla.zeta.org.au> To: bde@zeta.org.au, jb@cimlogic.com.au Subject: Re: Can't "make buildworld" Cc: freebsd-current@FreeBSD.ORG, wpub1@triton.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It was my recent addition of the MACHINE_ARCH test in src/Makefile that >(a) allowed src/Makefile to build world on alpha; and (b) caused the build >world on oldish systems to fail. In this case, I don't think the make ever >gets to the point of being able to make 'make' - with or without the -I. > >I guess the conclusion then is that the top level is doing too much. That's easy to fix using an ifdef like the one for editing .MAKEFLAGS, or just using the usual conditional expression for testing possibly- unset variables. I guess the conclusion is actually that make's (non) expansion of unset variables in ifdefs sucks. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message