NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/48579: #34490 (kernel compile fails in `le_isa_intredge', no'le' in kernel config)
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. Anyway exact error messages are
always appreciated, so that other users can also google it.
> > 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.
> 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."
> And what about strange FireWire driver problems?
I can't reproduce any problem, probably due to differnt procedures.
---
Izumi Tsutsui
Home |
Main Index |
Thread Index |
Old Index