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?
Thanks,
Matt.
Personally, I think LFS *should* go back to FSF binutils for the default book, unless and until there's a particular need for features present only in HJL's branch.
However, I also think it might be useful to make a note in the book about the HJL branch - I know for me, I didn't know about it for a long time.
-J- -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
