On Sun, Dec 4, 2011 at 12:39 PM, Bruce Dubbs <[email protected]> wrote:
> Tom Blamer wrote: > > I've been following the LFS 7.0 stable book exactly, as far as I know, > but > > I've hit a brick wall with building Bash in chapter 5. > > > > For example, I see lots of messages like this in the output of "make > tests": > > > > < ./glob.tests: command substitution: line 188: syntax error near > > unexpected token `)' > > < ./glob.tests: command substitution: line 188: `echo */man*/bash.*)' > > < ./glob.tests: command substitution: line 190: syntax error near > > unexpected token `)' > > < ./glob.tests: command substitution: line 190: `echo */man*/bash.*)"' > > > > My host system is Fedora 16, x86_64. > > > > There are at least four threads where other people had this problem or > > something similar, and no one ever reported what the issue was. What's > the > > deal? > > > http://www.linuxfromscratch.org/pipermail/lfs-support/2009-September/036410.html > > > http://www.linuxfromscratch.org/pipermail/lfs-support/2010-January/037338.html > > > http://linuxfromscratch.org/pipermail/lfs-support/2011-November/041616.html > > > http://www.linuxfromscratch.org/pipermail/lfs-support/2010-February/037873.html > > My first question is to ask what the output of the following is: > > sh --version > > Note that tests are not recommended in Chapter 5. Read the note in > section 4.6. > > -- Bruce > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > This is actually my second attempt going through this, the first time I hit similar bash errors in chapter 6 building glibc. So, after I started over, I ran the bash tests here in chapter 5 to see if I was still broken. [twblamer@localhost ~]$ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch Distributor ID: Fedora Description: Fedora release 16 (Verne) Release: 16 Codename: Verne [twblamer@localhost ~]$ uname -r 3.1.2-1.fc16.x86_64 [twblamer@localhost ~]$ /bin/sh --version GNU bash, version 4.2.20(1)-release (x86_64-redhat-linux-gnu) [twblamer@localhost ~]$ sh --version GNU bash, version 4.2.20(1)-release (x86_64-redhat-linux-gnu) su --login lfs lfs:~$ sh --version GNU bash, version 4.2.20(1)-release (x86_64-redhat-linux-gnu) # <-- still pulling from host lfs:~$ which sh /bin/sh lfs:~$ bash --version GNU bash, version 4.2.10(2)-release (x86_64-unknown-linux-gnu) lfs:~$ which bash /tools/bin/bash My stab in the dark is that this could have something to do with yacc. My first attempt on this host system, the bash build broke because I didn't have a yacc binary in my PATH. I installed the Fedora 16 byacc package and that gave me a yacc binary. Someone else said that installing bison fixed this problem for them, but I installed that first and it didn't help. On Fedora 16, installing bison gives me some yacc-related header files, but no yacc binary, hence why I had to install byacc. Also, even if I'm pulling the wrong /bin/sh during the build, how would that break the finished binary of bash? It seems like a parser problem within the bash source (induced by environment, header files or whatever). lfs:~$ yacc -V yacc - 1.9 20101229 lfs:~$ which yacc /usr/bin/yacc
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
