From owner-freebsd-qa Mon Mar 12 13: 2:13 2001 Delivered-To: freebsd-qa@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 282CC37B718; Mon, 12 Mar 2001 13:02:11 -0800 (PST) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id F13719D3; Mon, 12 Mar 2001 13:02:06 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA15763; Mon, 12 Mar 2001 13:02:06 -0800 (PST) Message-ID: <3AAD394D.49597B93@cup.hp.com> Date: Mon, 12 Mar 2001 13:02:05 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Larry Rosenman , qa@FreeBSD.org, marcel@FreeBSD.org Subject: Re: cputype=486 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 12-Mar-01 Marcel Moolenaar wrote: > > John Baldwin wrote: > >> > >> It looks like strip is linked against /usr/lib/libc.a. > >> > >> Marcel, > >> > >> It looks like there may be a bug in buildworld. It seems that static > >> binaries > >> are being linked against /usr/lib/libc.a rather than > >> /usr/obj/usr/src/i386/lib/libc/libc.a. > > > > In what stage? > > The final strip binary that will live in /usr/bin/strip on the target machine. Which is the one in: /usr/obj/usr/src/gnu/usr.bin/binutils/strip and not the one in: /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/binutils/strip Are we still talking about the same strip(1)? > > In short: Do not not build on Pentium with -march=pentiumsomething and > > then later install on non-pentiums! > > Uh, how can cross-builds _possibly_ work then???? If I do a i386 -> alpha > cross build does the alpha /usr/bin/strip get linked against the i386 > /usr/lib/libc.a on the host machine?? Of course not. The one that's being built as part of the cross-tools is however. > Or is libc treated magically by the > compiler? No. > For that matter, what if a static binary uses a new function added > to libc, how in the world will that link if we all our binaries against the > old libc during the world? That's just wrong. No, that's not wrong. Just think about it for a moment. You need to build cross tools first. Those must run on the build machine. You therefore build those exactly as you build anything else: you use the libraries on that machine. After you have built your cross tools, you can start building non-native libraries, against which you link the final non-native binaries. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message