Date: Sun, 2 Sep 2001 14:47:28 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Larry Rosenman <ler@lerctr.org> Cc: John Baldwin <jhb@FreeBSD.org>, freebsd-stable@FreeBSD.org, qa@FreeBSD.org, Eric Masson <e-masson@kisoft-services.com> Subject: Re: cputype=486 Message-ID: <20010902144728.A41762@dhcp01.pn.xcllnt.net> In-Reply-To: <20010902163046.A26933@lerami.lerctr.org> References: <20010901114903.D11062@athlon.pn.xcllnt.net> <XFMail.010901132212.jhb@FreeBSD.org> <20010901161054.B13047@athlon.pn.xcllnt.net> <20010902084832.B2510@lerami.lerctr.org> <20010902111131.B478@dhcp01.pn.xcllnt.net> <20010902163046.A26933@lerami.lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 02, 2001 at 04:30:47PM -0500, Larry Rosenman wrote: > > I was *VERY* surprised that a cross-build picked up *ANY* of the host > libraries for stuff running on the target. My logical brain ass/u/med > that a cross-build was totally safe from the libraries on the host > box. You simply assumed that different processor models within the same architecture would be treated as different architectures. This is not the case. As such, the build machine and the target machine are considered the same and will share the build tools. If they were treated as different architectures, they would not share the build tools and you would not (at least) have had this problem. > Obviously, I can't force any of this. Should I file a PR so it won't > get lost? Yes, please. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010902144728.A41762>