Jivin Robert P. J. Day lays it down ...
>
> sorry to pollute the list this much but i forgot to mention one more
> thing about my current uclinux nios2 patchset.
>
> i'm test building this kernel inside the absolutely latest,
> CVS-checked out uclinux surrounding infrastructure, so i'm not
> patching *anything* outside the kernel tree itself -- that is, nothing
> inside the top-level vendors/ directory, etc. in short, i'm assuming
> that any patches that used to be applied to the uclinux infrastructure
> back in, say, 20070130, are now part of the CVS repo. (if we're going
> to go bleeding edge, might as well go all the way.)
For the non-kernel portions of the dist the CVS repo is not bleeding
edge. It follows the dist releases and is currently at version
uClinux-dist-20070130.
If you wanted something more bleeding edge you could use the dist
snapshots that Gerg has been doing. Still, using CVS is probably
easier to manage at this point and close enough for us to easily merge.
> so, after a couple days of mucking around, here's my recipe for
> creating the entire build directory structure:
>
> 1) anonymously CVS check out uClinux-dist (CVS? gack. barf. :-)
>
> 2) git checkout the kernel tree into subdirectory linux-2.6.x/ inside
> that
>
> 3) apply my patchset to the linux-2.6.x/ directory, and patch
> absolutely nothing else
>
> and my recipe for test building a kernel (i'm not doing anything
> with user space stuff yet):
>
> $ make menuconfig
> $ make vendor_hwselect SPSYTF=...
Not sure what vendor_hwselect is, unless it's short hand for
some interactive process.
Building the dist with a 2.6 kernel is usually:
make config/menuconfig/xconfig
make
Everything else should get done for you.
> $ mkdir romfs [manually]
Why do you need to "mkdir romfs" ?
> $ NON_SMP_BUILD=1 make linux
Building the kernel is the first step, so the following will do:
make NON_SMP_BUILD=1
but
make NON_SMP_BUILD=1 linux
is also ok. On the bleeding edge dists you can run:
make single
> at that point, i get a pageful of warnings about some syscalls not
> being implemented, then the aforementioned error regarding
> asm/scatterlist.h:
>
> ...
> CC init/do_mounts.o
> In file included from include/linux/sunrpc/xdr.h:14,
> from include/linux/sunrpc/sched.h:18,
> from include/linux/sunrpc/auth.h:14,
> from include/linux/nfs_fs.h:42,
> from init/do_mounts.c:15:
> include/linux/scatterlist.h: In function `sg_set_page':
> include/linux/scatterlist.h:42: error: structure has no member named
> `page_link'
> ...
>
> and that's where i've left it for now.
>
> does all that make sense? i'll be back in a day or so to pick up
> where i left off.
Sounds ok so far.
Cheers,
Davidm
--
David McCullough, [EMAIL PROTECTED], Ph:+61 734352815
Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
