>> this is the way i've usually done things (since it was easier and
>> required less reboots), but i thought it was the other way around.  i
>> thought one was supposed to build a new kernel first so as to support
>> any new features that libraries or binaries might like to make use of.
>
>You do always want to build and install a new kernel first, but if you
>want a "make release" to work, as the person at the start of this
>thread did, you have to "make build" beforehand.

i see.  make a new kernel, then make build, and finally make a
release.  got it.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."