Re: kern/48579: #34490 (kernel compile fails in `le_isa_intredge', no'le' in kernel config)

[Zbigniew <zbigniew2011%gmail.com@localhost>]

The following reply was made to PR kern/48579; it has been noted by GNATS.

From: Zbigniew <zbigniew2011%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/48579: #34490 (kernel compile fails in `le_isa_intredge',
 no'le' in kernel config)
Date: Sat, 8 Feb 2014 17:45:30 +0100

 2014-02-08 14:15 GMT+01:00, Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>:
 > The following reply was made to PR kern/48579; it has been noted by GNATS.
 >
 > From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: tsutsui%ceres.dti.ne.jp@localhost
 > Subject: Re: kern/48579: #34490 (kernel compile fails in `le_isa_intredge',
 >       no'le' in kernel config)
 > Date: Sat, 8 Feb 2014 22:10:37 +0900
 >
 >  The PR says only:
 >  >> undefined references inside "le_isa_intredge" and "le_isa_attach"
 >
 >  and I got:
 >  ---
 >  if_le_isa.o: In function `le_isa_intredge':
 >  if_le_isa.c:(.text+0x18): undefined reference to `am7990_intr'
 >  if_le_isa.c:(.text+0x24): undefined reference to `am7990_intr'
 >  if_le_isa.o: In function `le_isa_attach':
 >  if_le_isa.c:(.text+0x518): undefined reference to `lance_copytobuf_contig'
 >  if_le_isa.c:(.text+0x522): undefined reference to
 > `lance_copyfrombuf_contig'
 >  if_le_isa.c:(.text+0x52c): undefined reference to `lance_copytobuf_contig'
 >  if_le_isa.c:(.text+0x536): undefined reference to
 > `lance_copyfrombuf_contig'
 >  if_le_isa.c:(.text+0x540): undefined reference to `lance_zerobuf_contig'
 >  if_le_isa.c:(.text+0x5df): undefined reference to `am7990_config'
 >  *** [netbsd] Error code 1
 >  ---
 >
 >  No idea if they are same or not.
 
 Yes, they look familar to me.
 
 >  Anyway exact error messages are
 >  always appreciated, so that other users can also google it.
 
 My guess was, it would be worthy to fix these errors rather, instead
 of leaving the problem to users and Google.
 
 >  >  >  Probably your problem is that you leave "bicc0 at isa? ..." line
 >  >  >  while you comment out "le* at bicc?" line.
 >  >
 >  >  I'm not sure, but maybe - still: does there exist any relationship
 >  >  between one and another?
 >
 >  if_le_isa.c is pulled by "bicc at isa" line
 >  via sys/dev/isa/files.isa:
 >   http://nxr.netbsd.org/xref/src/sys/dev/isa/files.isa?r=1.163#238
 >
 >  and MI am7990 driver (requried by all lance based drivers) is
 >  pulled by "le at bicc" line via sys/conf/files:
 >   http://nxr.netbsd.org/xref/src/sys/conf/files?r=1.1082#676
 >
 >  Then enabling bicc without "le* at bicc?" pulls only if_le_isa.c
 >  and it can't find MI lance functions.
 
 Well, maybe - but how do I know it reading the kernel configuration
 file? Especially, when "config" and "make depend" reveal no errors?
 
 >  >  Besides: why such problems aren't verified and reported during neither
 >  >  of TWO former stages: "configure KERNEL", and "make depend"?
 >
 >  We can avoid errors wrap most code in if_le_isa.c with
 >  #if NLE > 0 / #endif etc. but I'm not sure it's worth
 >  to allow such "bicc without le" settings that would simply say
 >  "le at bicc is not configured."
 
 Yes: I can confirm, that when each of the following lines are commented out:
 
 #nele0   at isa? port 0x320 irq 9 drq 7          # NE2100
 #le*     at nele?
 #ntwoc0 at isa? port 0x300 irq 5 iomem 0xc8000 flags 1  # Riscom/N2 sync serial
 #bicc0   at isa? port 0x320 irq 10 drq 7         # BICC IsoLan
 
 ...there is no "le-error" anymore.
 
 But could you, please, tell me: how the user is supposed to know, that
 "bicc requires le" in NetBSD's kernel configuration?
 
 >  >  And what about strange FireWire driver problems?
 >
 >  I can't reproduce any problem, probably due to differnt procedures.
 
 The procedure is rather simple:
 
 In the kernel configuration file - the one I sent - remove comment
 from beginning of the line:
 
 #fwohci* at pci? dev ? function ?       # IEEE1394 Open Host Controller
 
 There won't be any error during "config MYKERNEL" neither "make
 depend" stages - but the compilation will fail with several
 "fwohci"-related errors.
 
 The problem is, it is marked as pci?-dependent only (which is
 "switched on" already). My guess is, it needs another unrelated driver
 included into config, which pulls some header files - right? Which
 one?
 -- 
 regards,
 Zbigniew