From owner-freebsd-stable Fri Aug 27 13:54:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 1BF541556C for ; Fri, 27 Aug 1999 13:54:37 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id GAA43844; Sat, 28 Aug 1999 06:51:20 +1000 (EST) (envelope-from jb) Date: Sat, 28 Aug 1999 06:51:19 +1000 From: John Birrell To: Eliezer Rodriguez Gonzalez Cc: stable@FreeBSD.ORG Subject: Re: Some important environment variables. Message-ID: <19990828065118.A36761@freebsd1.cimlogic.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Eliezer Rodriguez Gonzalez on Fri, Aug 27, 1999 at 04:39:44PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 27, 1999 at 04:39:44PM -0400, Eliezer Rodriguez Gonzalez wrote: > > During my first (finally successfull) upgrade of my 2.2.6 system to 3.2 > stable I encountered, due to my ignorance, problems arising from the > lacking of the MACHINE_ARCH variable in my environment. I didn't know it > should be set before firing make aout-to-elf-build, although I realize (of > course) it should be set to i386 'cause I'm a PC user. If MACHINE_ARCH is undefined, it means i386 (historically in FreeBSD). MACHINE_ARCH should never by the user. Please don't suggest to people that they do that. If there is a problem with the aout-to-elf-build barfing because MACHINE_ARCH is not set, then a different fix is required. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message