* Marcel Moolenaar <[EMAIL PROTECTED]> [010901 18:10]:
> 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...
Is this a *NO*, we're not interested in fixing it?
If so, some BIG notices should be in /etc/defaults/make.conf around
the CPUTYPE setting.
I really think this should be fixed somehow....
(Not that I would know how...)
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
