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

[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: Sun, 9 Feb 2014 02:41:18 +0900

 >  My guess was, it would be worthy to fix these errors rather, instead
 >  of leaving the problem to users and Google.
 
 Incomplete reports make it harder to reproduce and confirm
 the problem to be fixed.  That's all.
 
 >  But could you, please, tell me: how the user is supposed to know, that
 >  "bicc requires le" in NetBSD's kernel configuration?
 
 IMO users who will edit kernel config are suppored to notice
 the "le at bicc" line has a parent "bicc at isa" line.
 Furthermore, users don't have to disable unnecessary devices.
 I.e. I'd say it's operational error and "don't do that."
 
 >  >  >  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.
 
 In the PR you wrote:
 >> 3. Comment out next two described lines - you'll see (in addition to the 
 >> former ones) very similar errors related to fwohci.
 and now you say remove one comment?
 
 >  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?
 
 If your claim is "kernel builds shouldn't fail if config(1) doesn't fail
 even if only parent devices are enabled" it would be ideally correct,
 but less worth to fix for me in these devices (unless patches are provided).
 In that case, the kernel will just say "ieee1394if is not configured"
 after the parent fwohci is attached and users can't use the target
 devices anyway.  It would be rather worse than link errors on build.
 
 ---
 Izumi Tsutsui