Date: Fri, 26 Jul 2002 10:48:45 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: "Bruce A. Mah" <bmah@FreeBSD.org>, "Brian J. McGovern" <bmcgover@cisco.com>, re@FreeBSD.org, qa@FreeBSD.org Subject: Re: Update for 4.6.1 issues Message-ID: <20020726074845.GB11087@sunbay.com> In-Reply-To: <XFMail.20020725162758.jhb@FreeBSD.org> References: <20020725191018.GB62517@sunbay.com> <XFMail.20020725162758.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--b5gNqxB1S1yM7hjW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 25, 2002 at 04:27:58PM -0400, John Baldwin wrote: >=20 > On 25-Jul-2002 Ruslan Ermilov wrote: > > On Thu, Jul 25, 2002 at 10:06:37PM +0300, Ruslan Ermilov wrote: > >> On Thu, Jul 25, 2002 at 02:52:48PM -0400, John Baldwin wrote: > >> >=20 > >> > On 25-Jul-2002 Ruslan Ermilov wrote: > >> > > On Thu, Jul 25, 2002 at 11:27:30AM -0700, Bruce A. Mah wrote: > >> > >> If memory serves me right, "Brian J. McGovern" wrote: > >> > >> > Is the examples issue a problem with CVS not checking them out?= Or is it an > >> > >> > issue of the release process not doing the right thing? I can't= do the first > >> > >> > (no commit privs), but I can look at the second over this comin= g weekend if > >> > >> > we think its a release process issue. > >> > >>=20 > >> > >> It's a release process problem, I think. I thought that Ruslan (= CC-ed) > >> > >> committed a fix for this problem to HEAD, but I don't know what t= he MFC > >> > >> status is. Maybe he can shed a little light on this? > >> > >>=20 > >> > > This was fixed in: > >> > >=20 > >> > > bsd.subdir.mk,v 1.44 (5.0-CURRENT) > >> > > bsd.subdir.mk,v 1.30.2.2 (4.6-STABLE) > >> > >=20 > >> > > A work-around for RELENG_4_6 (if it's wanted) is to replace the bs= d.subdir.mk > >> > > by bsd.prog.mk in share/examples/Makefile: > >> >=20 > >> > How big is the real fix? I personally wouldn't mind the workaround,= but if > >> > the fix isn't too big I'd rather just do it right to begin with. > >> >=20 > >> Quite big and not worth the effort IMHO, as it's not security-related. > >> Let's don't pollute the security branches with the non-security stuff. > >>=20 > > Better commit the kludge to RELENG_4_*'s bsd.lib.mk so that ports > > affected could still be built on these branches. (This fixes the > > bug where the missing LIB=3D would result in bsd.lib.mk attempting > > to build/install lib.a and lib_p.a.) >=20 > Is this in RELENG_4 as well? >=20 What, bug? It's been fixed in 4.6-STABLE by merging the new bsd.lib.mk from 5.0-CURRENT that does not have this problem. > Did we have this bug in 4.6-REL? >=20 Yep, once upon a time there was. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --b5gNqxB1S1yM7hjW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9QP7dUkv4P6juNwoRAhQXAJ9QYDBnuZAz0MJY6CuMNEd1XvcdeQCfQHRd pqoNVUJSzfds1MDZbEuFmjU= =qg2w -----END PGP SIGNATURE----- --b5gNqxB1S1yM7hjW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020726074845.GB11087>