i ended up getting it to sorta work with=20

./build.sh -m cobalt -u distribution
(for the cross compile)

then sending the destdir.cobalt to the other machine
i built the tools, then told it to install using the -D /usr/obj/destdir.co=
balt

it worked for the most part, but for some reason alot of permissions
got screwed up,
mysql, the chrooted named and ntpd, as well as the /tmp and /usr/tmp

just thought i would thank everyone and note it in case anyone else
tried to do it and had issues

i built the sets, but wasnt exactly sure how to install them inplace
except for a manual extracting of the tgz's and I didnt know if that
would screw something up so i just worked at it till I got build.sh to
work

-justin

On 5/13/05, Luke Mewburn <lukem@netbsd.org> wrote:
> On Wed, May 11, 2005 at 02:50:02PM -0400, Justin Newcomer wrote:
>   | hey
>   |
>   | I have a cobalt qube, which isnt the fastest processor in the world,
>   | so I want to cross compile my userland (i already cross compiled my
>   | kernel)
>   |
>   | doing the cross compile is no big deal, i have it done already
>   | but once I have all the new binaries, I cant figure out how to do the=
 install
>   |
>   | ./build.sh -u install=3D/
>   | would only work if it was a local machine
>   | and i dont really wanna / cant take my qube's hard drive out
>   | ( my cross compile environment is running in vmware )
>=20
> I use
>         ./build.sh [options] distribution sets
>=20
> This will build all of userland and create sets a la "build.sh release",
> without building all the release kernels & floppies that a full
> "build.sh release" does.
>=20
>=20
>