Ch. 6 GCC testing: program timed out

Kevin Alm kevinalm at fbx.com
Thu Sep 2 22:13:56 PDT 2004


----- Original Message -----
From: "Jeremy Utley" <jeremy at jutley.org>
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Sent: Friday, September 03, 2004 10:29 PM
Subject: Re: Ch. 6 GCC testing: program timed out


> On Fri, 2004-09-03 at 17:35, David Murphy wrote:
> > Greetings. I'm installing LFS 5.1.1 on an old Toshiba laptop with a
Pentium
> > 133 (which I don't suggest to anyone who doesn't have a week or two to
> > kill). Most of the results of the Chapter 6 GCC tests pretty much follow
> > what the book has to say about them, but during the actual "gcc tests"
> > section, I got the following:
> >
> > -----
> > Running
/sources/gcc-3.3.3/gcc/testsuite/gcc.c-torture/compile/compile.exp
> > ...
> > WARNING: program timed out.
> > FAIL: gcc.c-torture/compile/20001226-1.c,  -O1
> > WARNING: program timed out.
> > FAIL: gcc.c-torture/compile/20001226-1.c,  -O2
> > WARNING: program timed out.
> > FAIL: gcc.c-torture/compile/20001226-1.c,  -O3 -fomit-frame-pointer
> > WARNING: program timed out.
> > FAIL: gcc.c-torture/compile/20001226-1.c,  -O3 -g
> > WARNING: program timed out.
> > FAIL: gcc.c-torture/compile/20001226-1.c,  -Os
> > -----
> >
> > Could these possibly be a product of a slow processor, or is it likely
> > something more sinister?
> >
>
> The slow processor is exactly why this happens.  The tests take longer
> than the expect script running them think it should, so it times out.
> Seems to start happening on anything below about 300 MHz, in my
> experience.
>
> Don't worry about it.
>
> -J-
>
At a guess I would say the 133 mhz is your problem, in which case I wouldn't
sweat it.. I know I got a few timeouts with my k6-3 450. I really can't
comment on those specific failures though.
Regards,
Kevin




More information about the lfs-support mailing list