Matthew Burgess wrote:
>Folks,
>
>I'm proposing we stop tracking/using HJL's binutils. Here's my
>reasons:
>
>1) It adds host dependencies of bison and flex
>2) Recent bugs with HJL (stripping libc.a) have been hard to diagnose
>
>and fix
>3) FSF recently released 2.16, bringing it back up to speed with
>modern
>features we were relying on HJL for.
>
>So, does anyone think we should still stick with HJL binutils, and if
>so, what are the compelling reasons for doing so?
It should be done on a case by case basis.
For the most part FSF should be fine, but if you are playing with the
new nptl support for sparc64/mips you will want HJL...
As always, we will have to swing back and forwards between HJL and FSF
as development continues...
FWIW 2.16.90.0.3 doesn't appear to have the same flex issues as
2.16.90.0.2
Regards
[R]
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
