Date: 24 Jul 2002 08:56:48 -0500 From: Craig Boston <craig@meoqu.gank.org> To: freebsd-stable@freebsd.org Subject: RE: Installation issues with 4.6.1 RC2 Message-ID: <1027519008.92966.10.camel@owen1492.it.oot>
next in thread | raw e-mail | index | archive | help
> I did a buildworld using CPUTYPE=i586 on a p3
> and tried to upgrade from 4.6-RELEASE in a 586 via
> nfs, which failed. I then did an install on the p3
> of the i586 build. Then I did a buildworld again,
> still with CPUTYPE=i586. After fixing some problems
> with libtelnet.a not having been built (which didn't
> break the install on the p3, but did on the 586), an
> nfs install worked.
I've seen the same thing, building an i586 build on a machine which the
system libraries are built for i686. It seems some of the bootstrap
tools ("install" is the one that kept biting me) are getting linked
against the system libraries and then used in installworld.
Perhaps it would be best, as the last thing in buildworld, to rebuild
all of the bootstrap tools with the compiler and libraries for the
target system. How is this handled in cross builds like alpha?
I believe this has been discussed on -stable before, but I can't seem to
find it in the archives and don't know if there was any resolution other
than the workaround of installing the i586 build on the build system and
buildworlding again.
Craig
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?1027519008.92966.10.camel>