On Monday 16 January 2006 13:47, Ken Moffat wrote:
> > Well then, back to start.
> Sorry, I misread your post and thought you were in chapter 6.
> But, you haven't reached 5.7, you are still in 5.6.
Neither, nor. I was in chapter 6 and I did go to start. Nothing from
the last mailing ist still here
> But now that I realise you are in chapter 5, I expect c++ builds to
> fail until you have built gcc a second time - the first gcc is built
> with enable-languages=c. So, going back to your original question:
Well, I did so. I built LFS from a formated partition this morning.
I came to 5.6 and absolutly everything went fine, 5.7 too. Now I am in
5.11. GCC-3.4.3 - pass 2. I patched it, in the sources directory,
changed to gcc-3.4.3 and built gcc-build and went in. I copied
../gcc-3.4.3/configure --prefix=/tools \
--libexecdir=/tools/lib --with-local-prefix=/tools \
--enable-clocale=gnu --enable-shared \
--enable-threads=posix --enable-__cxa_atexit \
--enable-languages=c,c++ --disable-libstdcxx-pch
as written in the Book.
Made "make" several times, but "make check" allways gave me
Errors. So I made "make bootstrap" ans the "make check"
nothing else than errors.
Here are the last lines:
__________________________________________________________
WARNING: Couldn't find the global config file.
Test Run By lfs on Mon Jan 16 13:48:21 2006
Native configuration is i686-pc-linux-gnu
=== libstdc++ tests ===
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description
file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file
for target.
Using
/mnt/lfs/sources/gcc-3.4.3/libstdc++-v3/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/mnt/lfs/sources/gcc-3.4.3/libstdc++-v3/testsuite/libstdc++-dg/normal.exp
...
XPASS: 22_locale/locale/cons/12658_thread.cc execution test
FAIL: ext/enc_filebuf/char/13189.cc (test for excess errors)
WARNING: ext/enc_filebuf/char/13189.cc compilation failed to produce
executable
FAIL: ext/enc_filebuf/wchar_t/13189.cc (test for excess errors)
WARNING: ext/enc_filebuf/wchar_t/13189.cc compilation failed to produce
executable
=== libstdc++ Summary ===
# of expected passes 2718
# of unexpected failures 2
# of unexpected successes 1
# of expected failures 6
make[3]: *** [check-DEJAGNU] Error 1
make[3]: Leaving directory
`/mnt/lfs/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3/testsuite'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/mnt/lfs/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3/testsuite'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory
`/mnt/lfs/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3'
make: *** [check-target-libstdc++-v3] Error 2
==========================================================0
> (i) you looked at the output, but you showed us a failing program
> instead of the associated error message (search for 'Error' with a
> capital 'E').
HTH :->>>
> (ii) you probably didn't find the correct failure - almost always, a
> configure script will generate lots of failure messages because it
> tests for things that you don't have. Mostly, you need to find the
> _last_ 'Error' message.
I do have 2 unexpected failures. I dont care about expected failures.
BTW, runtest didn't show irregularities
Just another question: From where on can I restart securely when having
to switch off the machine?
Kind regards
Clemens
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
