On 12/27/05, Ken Moffat <[EMAIL PROTECTED]> wrote: > My memory is getting hazy (been a long day), but I have a suspicion > that bison might also be affected by the missing gettext.
I'm moving flex and gettext up in the build. We'll see what happens. > The big hassle is trying to make sense of differences - you'll know > that the diffs of binaries are at best hard to read So far, I haven't really bothered with viewing the binary diffs. What I've done so far has been tackling the real obvious issues. Some of these, like vim, will probably require more digging. There were no differences in the build logs for me. I recall sometime back when reading the archives that a strings dump can sometimes be helpful. > > I'm gonna try to get flex linked > > into bison and see if that cleans up the differences. Do you think I > > should move flex up in Ch. 6 or add bison and flex to Ch. 5? > > We all know how much everybody groans at yet another package in chapter > 5, so if it's fixed by reordering chapter 6, that would be more > acceptable. Yeah, yeah. As I said above I moved up flex and gettext in Ch. 6. Hopefully this will kill both the bison and e2fsprogs differences. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
