[uClinux-dev] one more note about my nios2 patches for git kernel

[Robert P. J. Day]

On Thu, 25 Oct 2007, David McCullough wrote:

> 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.

really?  that's just weird, having the CVS repo lagging behind tarball
snapshots.  what's the rationale for *that*?  it certainly flies in
the face of standard convention.

> >   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.

these instructions are not being done from within the kernel
directory, they're being done one level up in the uclinix top-level
directory.  that may be where you're getting confused.

> 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" ?

because the default uclinux "make" target wants a destination
directory for INITRAMFS_SOURCE.  if that directory doesn't exist, the
make complains.  you can also, AFAICT, run "make romfs", but just
creating the directory explicitly with "mkdir" seems sufficient.

> > $ 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

ok, i'll take your word for it, i've never seen that before.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================