On Fri, 12 Nov 2010 00:34:31 +0300
Flan Alflani <falfl...@gmail.com> wrote:

> 2010/11/11 littlebat <dashing.m...@gmail.com>:
> > On Wed, 10 Nov 2010 16:31:50 +0000
> > dgfhfgh dfghdfgh <solo9...@hotmail.com> wrote:
> >
> >>
> >>
> >>
> >> Sincerely,
> >>
> >> http://www.Q8h.net
> >>
> >>
> >>
> >> > Date: Tue, 9 Nov 2010 23:04:33 +0800
> >> > From: dashing.m...@gmail.com
> >> > To: lfs-support@linuxfromscratch.org
> >> > Subject: Re: Problem Booting up the new system ?
> >> >
> >> > On Tue, 9 Nov 2010 12:04:05 +0000
> >> > dgfhfgh dfghdfgh <solo9...@hotmail.com> wrote:
> >> >
> >> > >
> >> > > Hello all,
> >> > > after going thought the book  and try to boot the new system,
> >> > > the Bootloader work fine but when i try to boot the root
> >> > > filesystem my screen display  alot of color (attached photo)
> >> > > without any message or anything. I try to do the book again
> >> > > it seem to be compiling ok without anything i could find. dont
> >> > > know what i did wrong and or what to do next, therefore, if
> >> > > anyone could help or point me to the right direction. thxbook
> >> > > SVN-20101027host lfcliveCD
> >> >
> >> > Maybe, you can attach your .config file to the list, so someone
> >> > can test it on their machine.
> >> >
> >> > Maybe, you can copy your LFS root directory to another machine to
> >> > test if it is only happen on that machine.
> >> >
> >> > --
> >> > littlebat
> >> > --
> >> > http://linuxfromscratch.org/mailman/listinfo/lfs-support
> >> > FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> >> > Unsubscribe: See the above information page
> >>
> >> sorry forget to add the attachment :) here is a link
> >> http://linuxfromscratch.pastebin.com/mxmgFkV8
> >>
> >
> > I tested your .config on my LFS6.6 system, I didn't change anything
> > else except my system is vmware i386 machine, so the kernel config
> > program changed some things automatically, see the "diff" result
> > between the modified .config and yours:
> > http://linuxfromscratch.pastebin.com/DLuCd850
> >
> > Boot from the new compiled kernel, no any exception happened. After
> > compiled the vmware disk driver(Fusion MPT device support) into
> > kernel, I can boot and login into system with this kernel without
> > error.
> >
> > So, I think maybe your hardware need some special kernel configs or
> > your hardware has run into some new kernel bugs. I think.
> >
> > Good luck.
> >
> > littlebat
> > --
> > 开源文化实验室 http://www.learndiary.com/
> > 孟大兴网站 http://www.openlong.com/
> > --
> > http://linuxfromscratch.org/mailman/listinfo/lfs-support
> > FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> > Unsubscribe: See the above information page
> >
> 
> 
> littlebat,
> 
> thx for looking into my problem, However i have  a question on chapter
> 6.16. GCC-4.5.1  about the test suite results ?
> 
> Is this ok :
> 
> 
> ../gcc-4.5.1/contrib/test_summary
> cat <<'EOF' |
> LAST_UPDATED: Obtained from SVN: tags/gcc_4_5_1_release revision
> 162774
> 
> Native configuration is x86_64-unknown-linux-gnu
> 
>               === gcc tests ===
> 
> 
> Running target unix
> FAIL: gcc.c-torture/compile/limits-exprparen.c  -O0  (test for excess
> errors) FAIL: gcc.c-torture/compile/limits-exprparen.c  -O1  (test
> for excess errors) FAIL: gcc.c-torture/compile/limits-exprparen.c
> -O2  (test for excess errors) FAIL:
> gcc.c-torture/compile/limits-exprparen.c  -O3 -fomit-frame-pointer
> (test for excess errors) FAIL:
> gcc.c-torture/compile/limits-exprparen.c  -O3 -g  (test for excess
> errors) FAIL: gcc.c-torture/compile/limits-exprparen.c  -Os  (test
> for excess errors)
> 
>               === gcc Summary ===
> 
> # of expected passes          61316
> # of unexpected failures      6
> # of expected failures                165
> # of unsupported tests                833
> /sources/gcc-build/gcc/xgcc  version 4.5.1 (GCC)
> 
>               === libgomp tests ===
> 
> 
> Running target unix
> 
>               === libgomp Summary ===
> 
> # of expected passes          1029
>               === libmudflap tests ===
> 
> 
> Running target unix
> FAIL: libmudflap.c/pass46-frag.c (-O2) (test for excess errors)
> FAIL: libmudflap.c/pass46-frag.c (-O2) (test for excess errors)
> FAIL: libmudflap.c/fail31-frag.c (-O3) output pattern test
> FAIL: libmudflap.c/pass45-frag.c (-O3) execution test
> FAIL: libmudflap.c/pass45-frag.c (-O3) output pattern test
> FAIL: libmudflap.c/pass45-frag.c (-O3) execution test
> FAIL: libmudflap.c/pass45-frag.c (-O3) output pattern test
> FAIL: libmudflap.c/pass46-frag.c (-O3) (test for excess errors)
> FAIL: libmudflap.c/pass46-frag.c (-O3) (test for excess errors)
> FAIL: libmudflap.c++/pass41-frag.cxx execution test
> FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
> FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
> FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test
> 
>               === libmudflap Summary ===
> 
> # of expected passes          1414
> # of unexpected failures      13
>               === libstdc++ tests ===
> 
> 
> Running target unix
> 
>               === libstdc++ Summary ===
> 
> # of expected passes          7071
> # of expected failures                95
> # of unsupported tests                339
> 
> Compiler version: 4.5.1 (GCC)
> Platform: x86_64-unknown-linux-gnu
> configure flags: --prefix=/usr --libexecdir=/usr/lib --enable-shared
> --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
> --enable-languages=c,c++ --disable-multilib --disable-bootstrap
> --with-system-zlib
> EOF
> Mail -s "Results for 4.5.1 (GCC) testsuite on
> x86_64-unknown-linux-gnu" gcc-testresu...@gcc.gnu.org &&
> mv /sources/gcc-build/./gcc/testsuite/gcc/gcc.sum
> /sources/gcc-build/./gcc/testsuite/gcc/gcc.sum.sent &&
> mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum.sent
> &&
> mv 
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum.sent
> &&
> mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc+
> +-v3/testsuite/libstdc+
> +.sum /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc+
> +-v3/testsuite/libstdc++.sum.sent &&
> mv /sources/gcc-build/./gcc/testsuite/gcc/gcc.log 
> /sources/gcc-build/./gcc/testsuite/gcc/gcc.log.sent
> &&
> mv 
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log 
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log.sent
> &&
> mv 
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log
> /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log.sent
> &&
> mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc+
> +-v3/testsuite/libstdc+
> +.log /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc+
> +-v3/testsuite/libstdc++.log.sent && true
> -- 
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page

How about your interesting boot screen? 

Gcc testing result is too complex to analyze for me. The results can be
different in different environments. For example, the results is
different when I set "MAKEFLAGS=-j 2" compare to don't set
"MAKEFLAGS=-j 2", and the result in my 32 bit system is also different
compare to 
http://www.linuxfromscratch.org/lfs/build-logs/6.6/core2duo/test-logs/076-gcc .
So after some simple studies on my Gcc test result, I just omited these
test FAILs when I build my first LFS6.6 :-) 

--
开源文化实验室 http://www.learndiary.com/
孟大兴网站 http://www.openlong.com/
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to