Date: Mon, 12 Mar 2001 22:59:24 GMT From: Larry Rosenman <ler@lerctr.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Marcel Moolenaar <marcel@cup.hp.com>, marcel@FreeBSD.org, qa@FreeBSD.org, =?US-ASCII?Q?Larry?= Rosenman <ler@lerctr.org> Subject: Re: cputype=486 Message-ID: <20010312.22592400@ler-freebie.iadfw.net> In-Reply-To: <XFMail.010312145155.jhb@FreeBSD.org> References: <XFMail.010312145155.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/12/01, 4:51:55 PM, John Baldwin <jhb@FreeBSD.org> wrote regarding R= e:=20 cputype=3D486: > On 12-Mar-01 Marcel Moolenaar wrote: > > 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 s= tatic > >> >> 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 targ= et > >> machine. > > > > Which is the one in: > > > > /usr/obj/usr/src/gnu/usr.bin/binutils/strip > Yes, it was the final binary installed onto the actual 486 that dumped= =20 core in > this case. > > 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=3Dpentiumsometh= ing 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 i3= 86 > >> /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. > Right, this isn't the cross tools one. This is the final one that get= s > installed onto the 486. _That_ one is broken. > >> 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 aga= inst=20 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 th= e > > libraries on that machine. After you have built your cross tools, yo= u > > can start building non-native libraries, against which you link the > > final non-native binaries. > We aren't talking about cross tools, we are talking about the final=20 binary > installed onto the 486. Actually, it's whatever strip binary is running as part of make=20 installworld.=20 If Marcel wants us to do some make installworld ROOT=3D/nfs/fw/... I ca= n,=20 but that's not how I was taught.=20 I usually do: make buildworld (on my P-III, now with CPUTYPE=3Di486) make buildkernel KERNCONF=3DIPFILTER-FW (set up for the 486) login to the 486 mount P-III:/usr/src /usr/src mount P-III;/usr/obj /usr/obj=20 make installworld make installkernel KERNCONF=3DIPFILTER-FW mergemaster reboot What is the SUPPORTED recipe now?=20 LER > -- > John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010312.22592400>