See my answer to Jim. I MEANT to compile with a HOST system that has
-march=pentiumpro executables, and compile a new world with CPUTYPE=i486
or
no CPUTYPE and expect the new code to run on the 486, correct method?
LER
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 3/12/01, 12:49:50 PM, John Baldwin <[EMAIL PROTECTED]> wrote regarding Re:
cputype=486:
> On 12-Mar-01 Larry Rosenman wrote:
> > Not in the log I posted. isatty is NOT that large, so what ever this is,
> > is after isatty in the executable.
> *sigh*
> isatty() is in libc. That's the only place that that code comes from.
> It doesn't live in the executable's object files or source at all, so
> it has to be coming from some copy of libc.
> > I wonder if something forgot to pick up the /usr/obj libraries, since the
> > HOST system *IS* compiled with -march=pentiumpro.
> Now that could be.
> > This is valid, isn't it? (to compile on one box, and install on another
> > with DIFFERENT /etc/make.conf settings)?
> Well, as Jim pointed out, not really. This is why releases are built
> from scratch inside of a clean "white-room" chroot. Regardless, the
> libc in /usr/obj should be used when compiling static binaries during
> world. (Dynamic binaries should still need to make sure they use
> /usr/lib/libc.so for their rpath, though if we don't use rpath, I guess
> they could be linked against the libc.so in usr/obj as well, but a
> bintools/linker person (jdp/obrien) should be asked about that
> to be sure).
> --
> John Baldwin <[EMAIL PROTECTED]> -- 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
