On 16.8.2013 0:09, Bruce Dubbs wrote: > Ken Moffat wrote: > >> On Thu, Aug 15, 2013 at 11:06:45AM -0500, Bruce Dubbs wrote: >>> bison. 1 failure. >>> CXX examples/calc++/examples_calc___calc__-calc++-scanner.o >>> g++: error: ./examples/calc++/calc++-scanner.cc: No such file or directory >>> g++: fatal error: no input files >>> compilation terminated. >>> >>> This matches what Ken saw a couple of days ago. May be specific to >>> building in chroot. >>> >> >> I'm still massaging my buildscripts and haven't managed to get >> bison > 2.7.1 to build with them. Only a few more functions to >> rename as km_, and then I'll have to go back to looking at the diff >> of the source. >> >> That last sentence of yours makes me wonder what might be different >> in chroot. Usually that comes down either to mounts, or to runtime >> deps. I start to wonder if something needs to be built sooner. But >> looking at the full text (wrapped by my mailer) I can't see anything >> missing : >> >> /bin/sh ./build-aux/ylwrap `test -f >> 'examples/calc++/calc++-scanner.ll' || echo >> './'`examples/calc++/calc++-scanner.ll .c >> examples/calc++/calc++-scanner.cc -- : >> g++ -I./examples/calc++ -g -O2 -MT >> examples/calc++/examples_calc___calc__-calc++-scanner.o -MD -MP -MF >> examples/calc++/.deps/examples_calc___calc__-calc++-scanner.Tpo -c >> -o examples/calc++/examples_calc___calc__-calc++-scanner.o `test -f >> 'examples/calc++/calc++-scanner.cc' || echo >> './'`examples/calc++/calc++-scanner.cc >> g++: error: ./examples/calc++/calc++-scanner.cc: No such file or >> directory >> g++: fatal error: no input files >> compilation terminated. >> >> It seems to me that build-aux/ylwrap is failing. That's a script >> which creates temporary files and always deletes them on exit. I >> don't see anything in it except /bin/sh, sed, and some coreutils >> programs. And we've got all of those. > > I think I may have it. It appears that it needs flex. There now seems > to be a circular dependency bison needs flex and flex needs bison. At > least for tests. > > I went into chroot where flex has already been built and all tests are > OK. Looking at the Makefile, I don't see an easy way to disable the > test. Perhaps it just needs a note saying that the test fails because > flex is not yet available. > > -- Bruce >
Or just move the flex after bison and explain (as did for autoconf and automake dep) that full testsuite can be ran after flex has been installed. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
