Date: Wed, 30 Jul 2003 10:24:42 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: Peter Wemm <peter@wemm.org> Cc: current@FreeBSD.org Subject: Re: Who is responsible for the install check goo in Makefile.inc1 Message-ID: <20030730072442.GA37041@sunbay.com> In-Reply-To: <20030730021209.0461F2A7EA@canning.wemm.org> References: <20030730113026.B18842@freebsd1.cimlogic.com.au> <20030730021209.0461F2A7EA@canning.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
[ Moved to -current ]=20
On Tue, Jul 29, 2003 at 07:12:09PM -0700, Peter Wemm wrote:
> John Birrell wrote:
[...]
> > The installworld check for a kernel with the new sigaction promptly
> > core-dumped sh with the unsupported syscall. I think this check should
> > be based on sysctl kern.osreldate, not just running the new shell to see
> > if it core dumps. Thats kind of sub-optimal because I normally associate
> > core dumps during build/installworld with a dodgy build. In this case,
> > the build wasn't dodgy... I just hadn't realised that I was missing a t=
oe.
>=20
> The problem is that some of the install scripts run the host /bin/sh *aft=
er*
> src/bin has been installed. If your sh in ${OBJDIR} wont run, you *WILL*
> be hosed later on in the build with about a 50:50 split between old and n=
ew
> worlds. I dont recall which scripts are the culprits, but it is a side
> effect of "#! /bin/sh" that is on a script that is run during installworl=
d.
>=20
> In theory, the 'make installworld' stuff copies everything needed for an
> installworld to a /tmp directory, but it still misses a bunch of
> "#! /bin/sh" type things. This isn't a cross build issue because the she=
ll
> scripts are run on the host.
>=20
> For what its worth, this test saved me yesterday when I was trying to upd=
ate
> an ancient ia64 box to -current.
>=20
That wasn't the point John was trying to make, IMO.
I'm regularly upgrading 4.0-RELEASE to 5.x-CURRENT to check that
the upgrade path wasn't broken, and this check comes very handy.
I wouldn't object though if it was done using kern.osreldate.
I'd happily test any patches in this direction for you, John.
Cheers,
--=20
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software Ltd,
ru@FreeBSD.org FreeBSD committer
--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE/J3K6Ukv4P6juNwoRAhQXAJ97zb9tdphHsNVAIx9XneA/Ic/mqwCcDa+0
l/UHq7IigjRLaiL7Yhlshrs=
=kD8g
-----END PGP SIGNATURE-----
--BXVAT5kNtrzKuDFl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030730072442.GA37041>