From owner-freebsd-stable Sat Sep 1 16:11:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id D51CE37B405; Sat, 1 Sep 2001 16:10:59 -0700 (PDT) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f81NAtU36576; Sat, 1 Sep 2001 16:10:55 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.11.6/8.11.5) id f81NAsj13067; Sat, 1 Sep 2001 16:10:54 -0700 (PDT) (envelope-from marcel) Date: Sat, 1 Sep 2001 16:10:54 -0700 From: Marcel Moolenaar To: John Baldwin Cc: freebsd-stable@FreeBSD.org, qa@FreeBSD.org, Eric Masson , Larry Rosenman Subject: Re: cputype=486 Message-ID: <20010901161054.B13047@athlon.pn.xcllnt.net> References: <20010901114903.D11062@athlon.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 01, 2001 at 01:22:12PM -0700, John Baldwin wrote: > > >> > >> Is *ANYTHING* going to be done about this ever? It appears nothing > >> was done at all during the 4.4 cycle. > > > > If I have some time (yeah, right :-) I'll take a look at it. The > > quickest fix would be to define CPUTYPE as empty when building > > cross- and build-tools. This should override any definitions that > > are present in /etc/make.conf. > > That doesn't help. The problem is that the cross-tools built during buildworld > are linked against the hosts' libc.a, and then run on the target machine in > installworld. Thus, in this case you end up running a 686 libc.a in the cross > tool on a 486 and it blows up. > Ah yes. In that case it only works if you link shared, but then you have different problems. I guess this rules out CPUTYPE as a generic tunable. If you want the highest possible performance, you give up on portibility. You can't have it both... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message