On Thu, Aug 15, 2013 at 04:00:01PM -0500, Bruce Dubbs wrote: > Ken Moffat 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 working on this one. > > > 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 : > > [snip] > > > > 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. > > That's good info. I'll use that for more investigation. Thanks. > I've now got a new plan for my build failure (I can _untar_ using my script, but running configure in the script causes the build to fail). The logs from configure are *identical*. So now I'm going to save the directory from each after configure has completed and diff them. <sigh/> No idea what will show up, nor how long this is going to take. It occurs to me that a similar process in chroot (when bison has been configured but not built) and outside chroot might shed light on the test failure. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
