On Fri, Jan 18, 2013 at 9:32 AM, Giuseppe CONDORELLI < [email protected]> wrote:
> Yes Martin, > > but I discovered the issue building (erroneously because eglibc was > actually > not required at all) an external-toolchain a little bit old (gcc and > binutils) against the master oe-core repository, > which contains eglic-2.16 as you know. And libc/configure comes with the > issue I highlighted. > So, please, think to my patch as a nice to have and not as a mandatory one. > I don't know if other people will fall in my same condition. > > Thanks so much for your support. > Giuseppe > And are you using eglibc-2.16 built with binutils-2.19 in runtime on some targets? 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. http://sourceware.org/git/?p=glibc.git;a=commit;f=configure.in;h=bec039bcefe6a0494a249e2b78e112a0ab60893b This commit also doesn't say why.. Cheers,
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
