--r7U+bLA8boMOj+mD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 31, 2004 at 03:26:10AM +0530, Anand Lalgondar wrote:
> Hello,
>=20
> I performed the following to prepare a release packet in usr/src
>=20
> # ./build.sh -m evbmips -a mipsel -d -D /usr/build -R /usr/release -O
> /usr/objects -T /usr/tooldir
>=20
> At some stage I got an error on 'checklist' module. I found-out the cause
> of error with some entries missing in
> /usr/src/distrib/sets/lists/comp/md.evbmips. I had not included a _new_
> header file entry which was updated in the Makefile of
> /usr/src/sys/arch/evbmips/include/Makefile.
>=20
> At this stage I had the toolchain and the build directory completed with
> the required tool-chain and binaries. No since I didn't know how to
> create release after this, I started the above procedure once again which
> took more than 1 hour.
>=20
> There must be some command to just create the release folder after
> updating some files in /usr/src/distrib/sets/lists/comp/md.evbmips. Could
> someone please help me out.
>=20
> As I have understood by reading some papers on "build.sh" framework, it
> first creates the required toolchain, then compiles the NetBSD system for
> the intended target and then creates a release directory. Can some-one
> please tell me the command to just create a release directory based on
> the above mentioned directories used.

You've been pointed to one option. Another option would be to use -u,=20
which does an update build. While it will go through all the build steps,=
=20
it won't actually rebuild existing items.

Take care,

Bill

--r7U+bLA8boMOj+mD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAa0hUWz+3JHUci9cRAjmiAJ9ZHG3cdphjfId8/yjoaYYRdROCKwCcCX1c
KCR2DrksFatUQkOhMdEBuKw=
=mn/p
-----END PGP SIGNATURE-----

--r7U+bLA8boMOj+mD--