Subject: Re: arch conflict on update
To: None <sigsegv@rambler.ru>
From: Bill Studenmund <wrstuden@netbsd.org>
List: port-sparc64
Date: 03/28/2005 13:12:36
--7qSK/uQB79J36Y4o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 21, 2005 at 09:47:10PM +0000, sigsegv@rambler.ru wrote:
> Matthias Scheler wrote:
> >In article <423EA1C1.9060700@rambler.ru>,
> > sigsegv@rambler.ru writes:
> >
> >>I think this is because 'uname -m' returns sparc64, even though=20
> >>everything is 32-bit. How can I override this sanity check?
> >
> >
> >Is there a reason why you don't use the safe road by building into a
> >destination directory and using "./build.sh ... install=3D/" afterwards?
> >You can also build as a non-root user that way.
> >
> > Kind regards
> >
>=20
> I don't understand, this is exactly what I did:
> http://mail-index.netbsd.org/port-sparc64/2005/03/21/0002.html
No, the difference between what you describe doing and what Matthias=20
suggests is that he suggests running build.sh twice. You are trying to go=
=20
from nothing to installing in / in one step. Try building everything=20
first, _then_ run build.sh with the "install=3D/" command.
The second run of build.sh should not actually build anything, just=20
install.
Take care,
Bill
--7qSK/uQB79J36Y4o
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iD4DBQFCSHNEWz+3JHUci9cRAp7VAJiFcDUsGBHk6gBM+uVQAaSGylExAJ0Z6toH
2Ecga3EAy8j5aej750J5IA==
=IpTP
-----END PGP SIGNATURE-----
--7qSK/uQB79J36Y4o--