[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 9 Sep 2014 20:24:21 +0000
From: Anish Bhatt <anish@...lsio.com>
To: Jim Davis <jim.epost@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next <linux-next@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"mchan@...adcom.com" <mchan@...adcom.com>,
"David S. Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>
Subject: RE: randconfig build error with next-20140909, in
drivers/net/ethernet/broadcom/cnic.c
This is caused by c99d667e8527 ("cnic : Cleanup CONFIG_IPV6 & VLAN check")
So I'm not really sure what the fix for this is. CNIC will properly only support
[m] or [n] when IPV6 is compiled as a module, but if you set SCSI_BNX2X_FCOE or
SCSI_BNX2_ISCSI to be in built, there is a 'select CNIC' that forces CNIC to be
inbuilt, even though this is not supported by Kconfig. I was under the
assumption that select will not forcibly change m to inbuilt (or perhaps I'm
missing some syntax suboption ?)
This is still fixable in SCSI_BNX2_ISCSI using the same logic used in the above
mentioned commit, but not so in SCSI_BNX2X_FCOE where it causes a recursive
dependency error (thought it is fixing the issue nevertheless), and none of the
other solutions I tried seemed to work either.
Looking at previous code, the earlier approach used to just disable ipv6 code
in such a situation.
-Anish
________________________________________
From: Jim Davis [jim.epost@...il.com]
Sent: Tuesday, September 09, 2014 7:38 AM
To: Stephen Rothwell; linux-next; linux-kernel; Anish Bhatt; mchan@...adcom.com; David S. Miller; netdev
Subject: randconfig build error with next-20140909, in drivers/net/ethernet/broadcom/cnic.c
Building with the attached random configuration file,
drivers/built-in.o: In function `cnic_get_v6_route':
cnic.c:(.text+0x3a4168): undefined reference to `ip6_route_output'
make: *** [vmlinux] Error 1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists