Firstly, thanks a bunch for your expedient response, second, LFS 6.1.1 isn't that crusty! And the reason for my using it is my inexperience in Linux caused me to reason out possibly jumping into something I've never done before when (obviously enough) I am not great at accomplishing what I've already done. Third, I exited chroot, tried to su - lfs thinking I had to be in that state to recompile gettext, but it denied me (forgive me if this is a very naive error :). So I just said screw it and compiled as the root that it dropped me into upon exiting. I erased the old stuff and reconfig/recompiled anew, then jumped back into chroot and still the same exact error. Nothing seemed weird about config/make of gettext either, though I was just watching instead of logging and stuff runs by fairly fast on my machine (amd 3500+ 1 gig ram). I'd rather not redo chapter 5 (if so I may take your advice and jump into 6.2) but if I need to in your opinion please let me know.
Again, thanks for all the help, Ellis ----- Original Message ----- From: Dan Nicholson <[EMAIL PROTECTED]> Date: Friday, September 1, 2006 8:23 pm Subject: Re: Error Making Binutils in Chapter 6 To: LFS Support List <[email protected]> > On 9/1/06, Ellis Wilson <[EMAIL PROTECTED]> wrote: > > Before getting to the issue, why aren't you trying out the new stable > LFS? 6.1.1 is old and crusty. > > http://www.linuxfromscratch.org/lfs/view/stable/ > > > ... > > make[3]: Entering directory '/sources/binutils-build/bfd/po' > > file=../../../binutils-2.15.94.0.2.2/bfd/po/'echo fr | sed > 's,.*/,,''.gmo \ > > && rm -f $file && PATH=../src:$PATH no -o $file > > ../../../binutils-2.15.94.0.2.2/bfd/po/fr.po > > /bin/sh: no: command not found > > make[3]: *** [fr.gmo] Error 127 > > ... > > > > I only include this part one, because I don't feel as if typing > all of > > it would be particularly necessary, and two because the problem > seems> clearly to be originating from a missing "no" command. Upon > searching> through the LFS site there are some old postings (2+ > years) mentioning > > missing gettext and something about PERL being configured or linked > > incorrectly. > > The problem isn't that it's looking for a `no' command. Take a look at > bfd/Make-in. It's trying to use $(MSGFMT), but configure didn't find > it, so it substituted "no" instead of bombing like good autotools > should. > > Anyway, $(MSGFMT) should be /tools/bin/msgfmt which comes with > gettext. Possibly this could be related to a perl issue, but I'd have > to dig into how msgfmt is built. Did you log the gettext build? Do you > have /tools/bin/msgfmt? You may want to leave the chroot and try to > build gettext again and see if there are any strange messages. > > -- > Dan > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
