<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 18, 2013 at 9:32 AM, Giuseppe CONDORELLI <span dir="ltr"><<a href="mailto:giuseppe.condorelli@st.com" target="_blank">giuseppe.condorelli@st.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":6">Yes Martin,<br>
<br>
but I discovered the issue building (erroneously because eglibc was actually<br>
not required at all) an external-toolchain a little bit old (gcc and<br>
binutils) against the master oe-core repository,<br>
which contains eglic-2.16 as you know. And libc/configure comes with the<br>
issue I highlighted.<br>
So, please, think to my patch as a nice to have and not as a mandatory one.<br>
I don't know if other people will fall in my same condition.<br>
<br>
Thanks so much for your support.<br>
Giuseppe</div></blockquote></div><br>And are you using eglibc-2.16 built with binutils-2.19 in runtime on some targets?</div><div class="gmail_extra"><br></div><div class="gmail_extra" style>My point is that if upstream developers decided to support binutils-2.20+ only, they probably had some reason to do it and failing configure check is better way to show you're building unsupported combination then something failing badly in runtime on target.</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style><a href="http://sourceware.org/git/?p=glibc.git;a=commit;f=configure.in;h=bec039bcefe6a0494a249e2b78e112a0ab60893b">http://sourceware.org/git/?p=glibc.git;a=commit;f=configure.in;h=bec039bcefe6a0494a249e2b78e112a0ab60893b</a><br>
</div><div class="gmail_extra" style>This commit also doesn't say why..</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Cheers,</div></div>