I have spent the last two days 'experimenting'. I am sort of stuck because I cannot get flex to compile, and the tests seem to need that. Make (version 3.0.17.*cd) is completing, but the make check fails and stops almost immediately (just as the 3.0.0 version did).
I am waiting for some suggestions from the flex ( https://sourceforge.net/p/flex/bugs/157/) people, and/or instructions from "bison" on how to run at least some of the tests without flex. On Sun, Sep 22, 2013 at 10:48 PM, Michael Felt <[email protected]> wrote: > i will try again with the tests. over the next few days. this sounds like > it may be a good way to learn probevue and/or dbx. And maybe remaster tprof, > > all as different ways to find where this test is doing a lot of "unknown" > activity. > > Michael > On Sep 21, 2013 6:03 AM, "Ken Moffat" <[email protected]> wrote: > >> On Sat, Sep 21, 2013 at 04:36:38AM +0100, Ken Moffat wrote: >> > Killed it after more than 200 minutes CPU - memory use hadn't >> > changed, it was still using as much CPU as it could get, nothing >> > more in the output. >> > >> Unfortunately, the new build didn't boot - looks as if ext4 isn't >> supported for '/' by the yaboot bootloader - so I started to back it >> up. Discovered that testsuite.dir/at-groups/24-stderr had grown to >> 2.4G. The first 19 lines are text, the twentieth line is "extremely >> long" (perhaps the rest of the file) and (eventually) renders as >> inverse question-marks (i.e. invalid UTF-8) when I try to browse >> it in vim. I've copied the first 1K with 'dd', I'll attach that. >> >> ĸen >> -- >> das eine Mal als Tragödie, dieses Mal als Farce >> >
