<div dir="ltr">Does Kconfig of the Linux kernel do anything like that? It seems like the kernel might have a similar problem, and I know that Kconfig is use in openembedded and the Linux kernel, so it wouldn't be a totally NIH effort either.<div>
<br></div><div>wt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 11:10 AM, Stefan Hajnoczi <span dir="ltr"><<a href="mailto:stefanha@redhat.com" target="_blank">stefanha@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Mar 01, 2013 at 04:44:46PM +0000, Michael Brown wrote:<br>
> On 01/03/13 15:32, Stefan Hajnoczi wrote:<br>
> >iSCSI booting does not work VLANs because the iBFT VLAN field is not<br>
> >being filled in. Without the 802.1Q VLAN Identifier from the iBFT, the<br>
> >operating system cannot connect to the iSCSI target.<br>
><br>
> Applied, with some modifications, thanks!<br>
><br>
> <a href="http://git.ipxe.org/ipxe.git/commitdiff/7426177" target="_blank">http://git.ipxe.org/ipxe.git/commitdiff/7426177</a><br>
> <a href="http://git.ipxe.org/ipxe.git/commitdiff/7d64abb" target="_blank">http://git.ipxe.org/ipxe.git/commitdiff/7d64abb</a><br>
<br>
</div>Cool, nice improvement, thanks!<br>
<div class="im"><br>
> Inspired by your patches, I also allowed VLAN support to be dropped<br>
> from builds that happen to contain VLAN-using drivers (e.g. Hermon):<br>
><br>
> <a href="http://git.ipxe.org/ipxe.git/commitdiff/77f64b1" target="_blank">http://git.ipxe.org/ipxe.git/commitdiff/77f64b1</a><br>
><br>
> In the process of testing these, I've noticed a problem with the<br>
> build process. Where the weak symbol is defined by an object other<br>
> than the object that refers to the symbol, then it's undefined<br>
> whether the linker will pull in the weak-symbol version or the<br>
> strong-symbol version. To ensure that the weak-symbol version is<br>
> used as desired, it would be necessary to force the<br>
> weak-symbol-defining object to be earlier in the link order than any<br>
> objects referring to that symbol.<br>
><br>
> This is particularly problematic for symbols referred to by drivers.<br>
> For example, hermon.o refers to vlan_find(). Since the driver's<br>
> object is the first object dragged in by the build process, there is<br>
> no opportunity for the weak version (in netdevice.o) to be defined<br>
> before hermon.o refers to it.<br>
<br>
</div>I'm not aware of a solution that continues to let the linker decide<br>
which objects to pull in. That part of the build process could be<br>
replaced by a custom tool which outputs an ordered list of object files.<br>
This list would be used on the linker command-line instead of a static<br>
library.<br>
<br>
It feels wrong to write a custom tool though :(.<br>
<span class="HOEnZb"><font color="#888888"><br>
Stefan<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><span style="color:rgb(102,102,102);font-family:Arial,Helvetica,sans-serif"><b>Warren Turkal</b><br>Site Reliability Engineer | <img src="https://lh6.googleusercontent.com/hyz76OkGgnUwiU5b-fZWpAjIcTm-SaytgiFJAbgc6A_dzWIRMpwuB1497LLBOhbB4GU7X04YXaB9B4Qth_bB042dxPIXbHONj8r6LCTlp6Mt3QQpj3c" width="67px" height="11px"><br>
<a href="mailto:wt@ooyala.com" target="_blank"><font color="#134F5C">wt@ooyala.com</font></a> | 650-961-3400<br><a href="http://www.ooyala.com/" target="_blank"><font color="#134F5C">www.ooyala.com</font></a> | <a href="http://www.ooyala.com/blog" target="_blank"><font color="#134F5C">blog</font></a> | <a href="http://www.twitter.com/ooyala" target="_blank"><font color="#134F5C">@ooyala</font></a></span>
</div>