lfs-guy wrote:
Armin,
Yes, I understand that. It is not a test failure, but a build failure.
I am NOT augmenting the build in any way (other than concatenating all
the build instructions into a single command line pushed through the
time function). This is even mentioned in Ch. 5.4 (see the CLI below).
If you look at the line below that threw the error, there is no testing.
The question proposed is if flex is required as a base standard, and if
such, shouldn't it be stated?
Actually bison is built before flex in Chapter 6. In my log for Bison in
Chapter 6, configure says:
checking for flex... no
checking for lex... no
and it builds fine.
(I do have flex on my host so the Chapter 5 build of does find it, but it
is not necessary.)
I note that in your original post that you have:
make[3]: Entering directory '/mnt/lfs/sources/bison-3.0.4'
LEX examples/calc++/calc++-scanner.cc
CXX examples/calc++/examples_calc___calc__-calc++.o
CXX examples/calc++/examples_calc___calc__-calc++-parser.o
make[3]: 'tests/bison' is up to date.
make[3]: Nothing to be done for 'tests/atconfig'.
make[3]: 'tests/atlocal' is up to date.
CC examples/mfcalc/examples_mfcalc_mfcalc-mfcalc.o
CC examples/rpcalc/examples_rpcalc_rpcalc-rpcalc.o
CXX examples/calc++/examples_calc___calc__-calc++-scanner.o
g++: error: ./examples/calc++/calc++-scanner.cc: No such
The LEX line does not complain, so it must be finding lex.
Looking at my log, I find it curious that my output in Chapter 5 is
different from yours even though the version of bison is the same.
extexi: GEN examples/calc++/calc++-driver.hh
extexi: GEN examples/calc++/calc++-driver.cc
extexi: GEN examples/calc++/calc++-parser.yy
extexi: GEN examples/calc++/calc++-scanner.ll
extexi: GEN examples/calc++/calc++.cc
On your host, what does /usr/bin/yacc look like?
$ file /usr/bin/yacc
/usr/bin/yacc: POSIX shell script, ASCII text executable
$ cat /usr/bin/yacc
#! /bin/sh
exec '/usr/bin/bison' -y "$@"
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
