Date: Sun, 20 Mar 2005 21:43:50 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: Chuck Robey <chuckr@chuckr.org> Cc: current@freebsd.org Subject: Re: aic7xxx/aicasm manpage Message-ID: <20050320194350.GA92555@ip.net.ua> In-Reply-To: <423DCAA0.9020104@chuckr.org> References: <Pine.NEB.3.96L.1050320190256.92228A-100000@fledge.watson.org> <423DCAA0.9020104@chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 20, 2005 at 07:10:24PM +0000, Chuck Robey wrote: > Robert Watson wrote: > >On Sun, 20 Mar 2005, Chuck Robey wrote: > > > > > >>My kernel build is busted, it can't find: > >> > >>cd ../../../modules;=20 > >>MAKEOBJDIRPREFIX=3D/usr/src/sys/amd64/compile/JULY/modules=20 > >>KMODDIR=3D/boot/kernel DEBUG_FLAGS=3D"-g" MACHINE=3Damd64=20 > >>KERNBUILDDIR=3D"/usr/src/sys/amd64/compile/JULY" make all > >>=3D=3D=3D> aac (all) > >>=3D=3D=3D> accf_data (all) > >>=3D=3D=3D> accf_http (all) > >>=3D=3D=3D> agp (all) > >>=3D=3D=3D> aha (all) > >>=3D=3D=3D> aic7xxx (all) > >>=3D=3D=3D> aic7xxx/aicasm (all) > >>make: don't know how to make aicasm.1. Stop > >>*** Error code 2 > >> > >>Stop in /usr/src/sys/modules/aic7xxx. > >>*** Error code 1 > >> > >>Stop in /usr/src/sys/modules. > >>*** Error code 1 > >> > >>I know that to fix this, the simplest way is to merely stick a NOMAN=3D > >><empty> > >> > >>into the Makefile at /sys/modules/aic7xxx/aicasm. I don't know if > >>that's the way you'd want to fix it, but it seems to break the build for > >>me, so a prompt fix is in order, I think.=20 > > > > > >Are you building a 6.x kernel from a 5.x userspace? You can work around > >it the documented way by using buildworld and the buildkernel, or the ea= sy > >way, by forcing NOMAN during the kernel build (or changing NO_MAN in the > >aicasm Makefile to NOMAN). There was discussion of adding compatibility > >bits to 5.x so it could build makefiles that use NO_MAN, but I've yet to > >see that work. Of course, my 5.x boxes where I build 6.x kernels aren't > >all that up-to-date... > > >=20 > This is a system that's having it's first new kernel being compiled, but= =20 > uname reports a 6.0 current, so I don';t think I've made any gross=20 > mistake, and the branch is HEAD, so I'm doing nothing at all with 5.x, I= =20 > think. I'm not using Make INSTALLKERNEL although I used to do that. >=20 > I already got past it by patching my Makefile, which I know is wrong,=20 > because I'm gonna have to take it out once it gets fixed. >=20 But your world (including /usr/share/mk/) is 5.x. If you had followed the src/UPDATING instructions closely, you wouldn't hit this problem: : To build a kernel : ----------------- : If you are updating from a prior version of FreeBSD (even one just : a few days old), you should follow this procedure. With a : /usr/obj tree with a fresh buildworld, : make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=3DYOUR_KERNEL_HERE : make -DALWAYS_CHECK_MAKE installkernel KERNCONF=3DYOUR_KERNEL_HERE The buildworld takes care of updating make(1), and src/Makefile takes care of using fresh share/mk files. And so on. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCPdJ2qRfpzJluFF4RAomWAKCC9nkJ8JVKrrOBdMyFzH7SVPdulQCdGz6m eVlw3W82l+SQL1xF52Rg22g= =8HBv -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050320194350.GA92555>