Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Mar 2001 22:21:17 GMT
From:      Larry Rosenman <ler@lerctr.org>
To:        Marcel Moolenaar <marcel@cup.hp.com>
Cc:        Larry Rosenman <ler@lerctr.org>, John Baldwin <jhb@FreeBSD.org>, qa@FreeBSD.org, marcel@FreeBSD.org
Subject:   Re: cputype=486
Message-ID:  <20010312.22211700@ler-freebie.iadfw.net>
In-Reply-To: <3AAD485E.272DF239@cup.hp.com>
References:  <XFMail.010312124506.jhb@FreeBSD.org> <3AAD394D.49597B93@cup.hp.com> <20010312.21272700@ler-freebie.iadfw.net> <3AAD485E.272DF239@cup.hp.com>

next in thread | previous in thread | raw e-mail | index | archive | help


>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 3/12/01, 4:06:22 PM, Marcel Moolenaar <marcel@cup.hp.com> wrote=20
regarding Re: cputype=3D486:


> Larry Rosenman wrote:
> >
> > > No, that's not wrong. Just think about it for a moment. You need t=
o
> > > 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 th=
e
> > > final non-native binaries.
> >
> > So what you are saying is cross build HOSTS have to suffer in perfor=
mance
> > while they are being used as the HOST?  Why should this be?

> No, what I'm saying is that if you have highly optimized code that
> includes CPU specific instructions, you'd better run them on compatibl=
e
> CPUs only.

> > In this case the make buildworld was done on a HOST that was built
> > -march=3Dpentiumpro, the make flags for the new build were with NO -=
march
> > (or with -m486), and then the make installworld dies with the SIGNAL=
 4,
> > on a PPRO instruction in whatever strip binary is run from install. =
 This
> > seems VERY wrong if we are going to support cross-environment builds=
 AT
> > ALL.

> No, it isn't wrong. You basicly introduce a third machine into the
> equation:

> 1. The build machine,
> 2. The target machine,
> 3. the install machine.

> In your case 1 is incompatible with 3. We don't support that (yet?).
> Make sure your installation machine is compatible with your build
> machine. The best approach is to make you install machine the same as
> your build machine and install over NFS to the target machine.

HOW?  I always did it:

make buildworld on the P-III
make buildkernel on the P-III for the 486
mount the /usr/src and /usr/obj for the P-III on the 486
cd /usr/src on the 486, make installworld=20
make installkernel
mergemaster
reboot

how do I do this now?=20



> --
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010312.22211700>