On Fri, Apr 11, 2008 at 1:23 PM, Bruce Dubbs <[EMAIL PROTECTED]> wrote: > Sukucorp Sukucorp wrote: > > On Fri, Apr 11, 2008 at 2:48 PM, <[EMAIL PROTECTED]> wrote: > >> + <para>[bdubbs] - Updated host requirments to check for > >> + symbolic links from sh, awk, and yacc.</para> > > > > Was there a bug report for this or did anyone run into any problems? > > > > I don't know about bison/yacc, but I did not have any issues starting > > from a host where sh was linked to dash and awk was linked to mawk. My > > host was Ubuntu where gawk is not installed. I bypassed updating the > > host by installing gawk before building pass1 binutils. > > I was responding to some earlier comments about sh->dash causing problmes. I > added the part about yacc and awk because I know thy are sometimes used, but > I > don't know for sure if they are essential for LFS. It is just making sure. > I > started to add lex, but I didn't see flex required.
yacc (bison) - Definitely needed since we patch the bash parse.y file in Ch. 5 and yacc will need to be rerun. Could add bison to Ch. 5 before bash, but IMO it's easier for the host to just install bison. awk - Definitely needed by the glibc build, and gawk in particular due to use of some non-portable features. lex - Nothing yet. bash - Not needed for actual building, but glibc's ldd and tzselect need either bash or ksh to work. The values will be substituted at configure time. I don't know what happens without them, and it's probably not that important in Ch. 5 if those utilities aren't there. However, we create the LFS user with /bin/bash as the login shell, and this can't be substituted as is because we set up the environment through the bash initialization files. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
