Date: Tue, 19 Nov 2013 16:02:45 -0500 From: "illoai@gmail.com" <illoai@gmail.com> To: Mason Loring Bliss <mason@blisses.org> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Kernel build error (9.2 on 9.1 userland) Message-ID: <CAHHBGkqH%2BkOXsprHbiCxyfGBaaPQQJcwD7BfD%2Btg3hzYYwtv5w@mail.gmail.com> In-Reply-To: <20131119200931.GE13289@blisses.org> References: <20131119200931.GE13289@blisses.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 November 2013 15:09, Mason Loring Bliss <mason@blisses.org> wrote: > Hi there! I'm not an experienced FreeBSD user yet, but I'm interested in > doing more with it. > > I've got a FreeBSD 9.1 system that I've been updating with freebsd-update, > but since I use a custom kernel (it's a Xen PV domU) I've been building my > kernel separately. It just occurred to me that freebsd-update doesn't likely > touch my /usr/src. So, today I updated /usr/src to base/stable/9 and tried to > build, but my kernel build errors out. > > I'm wondering why the build is breaking on what should updated, pristine > source from the stable tree. Is building on 9.1 the issue, and I'm seeing > some conflict with the headers in my userland? What do I want to follow > instead of base/stable/9 to get bug fixes and such for 9.1? I see > base/release/9.1.0. Does that get security updates to match what > freebsd-update will download for me for stock items? > > cc1: warnings being treated as errors > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c: In function 'nfsrv_sattr': > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2313: warning: implicit declaration > of function 'NFSGETTIME' > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2313: warning: nested extern > declaration of 'NFSGETTIME' [-Wnested-externs] > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c: In function 'nfsv4_sattr': > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2443: warning: passing argument 1 of > 'nfsv4_strtouid' from incompatible pointer type > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2443: warning: passing argument 2 of > 'nfsv4_strtouid' makes pointer from integer without a cast > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2443: warning: passing argument 3 of > 'nfsv4_strtouid' makes integer from pointer without a cast > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2443: warning: passing argument 4 of > 'nfsv4_strtouid' from incompatible pointer type > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2443: error: too few arguments to > function 'nfsv4_strtouid' > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2469: warning: passing argument 1 of > 'nfsv4_strtogid' from incompatible pointer type > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2469: warning: passing argument 2 of > 'nfsv4_strtogid' makes pointer from integer without a cast > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2469: warning: passing argument 3 of > 'nfsv4_strtogid' makes integer from pointer without a cast > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2469: warning: passing argument 4 of > 'nfsv4_strtogid' from incompatible pointer type > /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:2469: error: too few arguments to > function 'nfsv4_strtogid' > *** [nfs_nfsdport.o] Error code 1 > > Stop in /usr/obj/usr/src/sys/XEN. > *** [buildkernel] Error code 1 > > Stop in /usr/src. > *** [buildkernel] Error code 1 > > Stop in /usr/src. > > > The best I could do to identify my userland seems to be this, from > /usr/include/sys/syscall.h: > > * $FreeBSD: release/9.1.0/sys/sys/syscall.h 229724 2012-01-06 19:30:17Z jhb > > Thanks in advance for clues! :) You have some options: The simplest is to bring your /usr/src back to 9.1-whatever & build kernel from there. Even if you don't intend to install a custom-built world, you probably need to build [parts of] a 9.2 world to build a 9.2 kernel on a 9.1 system. Toolchain & headers & libs for starters. Alternately, you could freebsd-update to 9.2 & build a 9.2 kernel from there. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHHBGkqH%2BkOXsprHbiCxyfGBaaPQQJcwD7BfD%2Btg3hzYYwtv5w>