LFS 7.2 GCC test duration

Lancelot1 · 12-13-2012, 08:24 AM

In section 6.17 there is a GCC test that takes forever to complete. It has now been running for 6 hours.

make -k check

Is there anyway to split this or speed it up?

Keith Hedger · 12-13-2012, 08:37 AM

I got bored with waiting for the tests to finish when making my first LFS, so just quit them and figured if the compiler is fubar it will show up quite soon, I don't use the tests now, but thats just what I do

druuna · 12-13-2012, 08:39 AM

Quote:

Originally Posted by Lancelot1

In section 6.17 there is a GCC test that takes forever to complete. It has now been running for 6 hours.

That is a long time, although the (old/slow?) hardware used could be the culprit.

Quote:

Is there anyway to split this or speed it up?

If your CPU has multiple cores you could try this:

Code:

export MAKEFLAGS='-j 2'
make -k check

If you have 4 cores try 4 instead of 2.

This might not work. If you see messages like this *** Waiting for unfinished jobs.... then you need to unset MAKEFLAGS and be be patient....

Not running the tests isn't an option in my opinion (unless you have successfully installed LFS version X on platform Y multiple times already).

Lancelot1 · 12-13-2012, 08:40 AM

Quote:

Originally Posted by Keith Hedger

I got bored with waiting for the tests to finish when making my first LFS, so just quit them and figured if the compiler is fubar it will show up quite soon, I don't use the tests now, but thats just what I do

ok but that isn't for everyone. This is a learning curve for me so I don't want to skip it

re_nelson · 12-13-2012, 03:53 PM

Quote:

Originally Posted by Lancelot1

In section 6.17 there is a GCC test that takes forever to complete. It has now been running for 6 hours.

make -k check

Is there anyway to split this or speed it up?

That's not at all atypical and is quite hardware dependent. When I recently upgraded to GCC 4.7.2, it took some 8 hours to run and that's on a quad core system. Having built several instances of LFS, I've just grown accustomed to the long wait and prefer to run the checks or tests on all packages. Knowing how long it would take gave me an opportunity to cut the grass, trim the hedges and clean up the leaves in the yard. Thanks to LFS, I have a good-looking yard and got some much-needed exercise. What a versatile distro!

Lancelot1 · 12-14-2012, 02:20 AM

Quote:

Originally Posted by druuna

That is a long time, although the (old/slow?) hardware used could be the culprit.

If your CPU has multiple cores you could try this:

Code:

export MAKEFLAGS='-j 2'
make -k check

If you have 4 cores try 4 instead of 2.

This might not work. If you see messages like this *** Waiting for unfinished jobs.... then you need to unset MAKEFLAGS and be be patient....

Not running the tests isn't an option in my opinion (unless you have successfully installed LFS version X on platform Y multiple times already).

ok druuna thanks, will try it

Yeah my laptop is 3 years old so I guess there are some issues but still this shouldnt be a problem with linux.
I did see multi time outs on tests

re_nelson · 12-14-2012, 02:41 AM

Quote:

Originally Posted by re_nelson

When I recently upgraded to GCC 4.7.2, it took some 8 hours to run and that's on a quad core system.

Just for the record, I build GCC with ALL languages, including Ada, Java and Objective C as well as C and C++. So, even on a i5 quad core, it takes a long time to run.