freebsd stable - Sep 2003 - buildkernel errors with "options SMBFS"

Hi all... another lurker and first-time poster... if I forget something relevant
please let me
know...

Anyway, have tried to make a kernel on two different machines under the latest
(as of
04:37AM 4 September 2003 -0500 (EDT)) 4.9-PRERELEASE **AND** 5.1-p2 and get 
the error message as shown below.  I am including (at the end) the uname-a from
both
of the systems.  Each of them will compile this exact same kernel exactly right
if I leave
the "options SMBFS" line out of the kernel config file.  I will
happily post those files if you
deem them relevant but I am not now for space reasons.  

I have tried scanning the past few weeks of archives on this list but have found
nothing
particularly relevant, unless I simply missed it.  

This is reproducible every time, and the same exact error in the same exact
place
occurs on both the 4.9 and the 5.1 machine. 

I can find no other relevant information.  The discs are not full, and I did a
clean
buildworld (removed /usr/obj/* and made cleandir twice, then built the world)
first.

In fact, these were attempted builds on the exact same kernel config file,
without the
SMBFS option. 

I'm not terribly concerned about this, as I was just going to play around
with mounting
some NT exports, but it would be nice to know what is causing this. 

Peace,

 -- Daniel
 


tail output of `makeworld -j4 buildkernel KERNCONF=DAGESH` ::
-------------------------------------------------------

===> s3
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
awk -f @/tools/makeobjops.awk @/isa/isa_if.m -h
awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -
I@/../include -I/usr/obj/usr/src/i386/usr/include  
/usr/src/sys/modules/s3/../../dev/fb/s3_pci.c
===> vesa
touch opt_vga.h
machine -> /usr/src/sys/i386/include
touch opt_vesa.h
@ -> /usr/src/sys
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -
I@/../include -I/usr/obj/usr/src/i386/usr/include  
/usr/src/sys/modules/vesa/../../i386/isa/vesa.c 
/usr/src/sys/modules/vesa/../../dev/syscons/scvesactl.c
1 error
*** Error code 2
1 error
*** Error code 2
1 error


END tail output
==================================

uname -a for system #1
-------------------------------------------------------
FreeBSD chumash 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #1: Wed Sep  3 
19:45:08 EDT 2003     root@:/usr/obj/usr/src/sys/CHUMASH-SMP  i386


uname -a for system #2
----------------------------------------------------------
FreeBSD dagesh 5.1-RELEASE-p2 FreeBSD 5.1-RELEASE-p2 #0: Sat Aug 30 
16:16:03 EDT 2003     root@:/usr/obj/usr/src/sys/DAGESH  i386

On Thu, Sep 04, 2003 at 04:45:29AM -0400, Daniel wrote:
> Hi all... another lurker and first-time poster... if I forget something
relevant please let me
> know...
> 
> Anyway, have tried to make a kernel on two different machines under the
latest (as of
> 04:37AM 4 September 2003 -0500 (EDT)) 4.9-PRERELEASE **AND** 5.1-p2 and get
> the error message as shown below.  I am including (at the end) the uname-a
from both
> of the systems.  Each of them will compile this exact same kernel exactly
right if I leave
> the "options SMBFS" line out of the kernel config file.  I will
happily post those files if you
> deem them relevant but I am not now for space reasons.  
[...]

Make sure you have all of the necessary options in your kernel config file.
For smbfs, you need these:

options 	SMBFS
options 	NETSMB
options 	NETSMBCRYPTO
options 	LIBMCHAIN
options 	LIBICONV

... or you can just use kldload to load the right modules (smbfs.ko,
libiconv.ko, libmchain.ko) - kldload smbfs will drag them all in
automatically.


Tim

Wow, thanks!  I thought I had read LINT well enough but I missed this part!  Now
I feel
sheeeeeeeepish.  :)  Hopefully this helps another poor fool out too!  :)

It *would* be nice if the config parser at the beginning threw an error for
obvious
incompatible or known missing options like this ... ones that *will* throw an
error later in
the build.  There was nothing in LINT (particularly around the SMBFS line) to
indicate
these were necessary additional options whatsoever.

Anyway, thanks again and sorry for all the noise!

Peace all...

 -- Daniel
 <><

On 4 Sep 2003 at 21:59, Tim Robbins wrote:
> On Thu, Sep 04, 2003 at 04:45:29AM -0400, Daniel wrote:
> 
> > Hi all... another lurker and first-time poster... if I forget
something relevant please let me
> > know...
> > 
> > Anyway, have tried to make a kernel on two different machines under
the latest (as of
> > 04:37AM 4 September 2003 -0500 (EDT)) 4.9-PRERELEASE **AND** 5.1-p2
and get
> > the error message as shown below.  I am including (at the end) the
uname-a from both
> > of the systems.  Each of them will compile this exact same kernel
exactly right if I leave
> > the "options SMBFS" line out of the kernel config file.  I
will happily post those files if you
> > deem them relevant but I am not now for space reasons.  
> [...]
> 
> Make sure you have all of the necessary options in your kernel config file.
> For smbfs, you need these:
> 
> options 	SMBFS
> options 	NETSMB
> options 	NETSMBCRYPTO
> options 	LIBMCHAIN
> options 	LIBICONV
> 
> ... or you can just use kldload to load the right modules (smbfs.ko,
> libiconv.ko, libmchain.ko) - kldload smbfs will drag them all in
> automatically.
> 
> 
> Tim
>