Bug#175526: Bug #175526
> On Sun, Jan 19, 2003 at 07:48:04PM -0800, Jeff Bailey wrote:
> > I haven't seen mention of it on this list, so I wanted to bring it up -
> > Bug #175526 against glibc is m68k specific.
>
> interesting. I am running glibc-2.3 and gcc-3.2 without much problems
> here, will look if I can see something obvious.
I'm building m68k gcc over 11 days, and it's still testing...
The halfway result of build shows gcc-3.2-3.2.2ds3 is fine with
glibc-2.3.1-9. I need to build gcc-3.2-3.2.2ds3 in the 1st stage
using with gcc-2.95, because debian gcc-3.2 cannot build itself!
The original bug report (#175526) says:
> Looking at http://buildd.debian.org/build.php?arch=m68k&pkg=gcc-3.2
> you'll see that beginning with
>
> build 1:3.2.1ds5-0pre6 (latest build at Nov 14 04:53: successful)
>
> nearly all tests of the gcc testsuite begin to fail. This is the first
> build with glibc-2.3.1 installed.
>
> To investigate, please look at the build/gcc/testsuite/*.log files in
> the package directory.
Build 1:3.2.1ds5-0pre6 has a lot of testsuite failure:
=== g++ Summary ===
# of expected passes 222
# of unexpected failures 6314
# of unexpected successes 31
# of expected failures 945
# of unresolved testcases 15
# of untested testcases 23
# of unsupported tests 6
=== g77 Summary ===
# of unexpected failures 914
# of unresolved testcases 33
# of untested testcases 410
# of unsupported tests 8
=== gcc Summary ===
# of expected passes 417
# of unexpected failures 13902
# of unexpected successes 36
# of expected failures 20
# of unresolved testcases 4419
# of unsupported tests 118
=== objc Summary ===
# of unexpected failures 550
# of unresolved testcases 490
=== libjava Summary ===
# of expected passes 435
# of unexpected failures 689
# of expected failures 12
# of untested testcases 918
=== libstdc++-v3 Summary ===
# of unexpected failures 237
Build 1:3.2.1ds4-0pre5, the previous 1:3.2.1ds5-0pre6, has less
failure:
=== g++ Summary ===
# of expected passes 7303
# of unexpected failures 3
# of unexpected successes 1
# of expected failures 88
# of untested testcases 23
# of unsupported tests 6
=== g77 Summary ===
# of expected passes 1424
# of unexpected failures 14
# of unresolved testcases 14
# of unsupported tests 8
=== gcc Summary ===
# of expected passes 18259
# of unexpected failures 74
# of expected failures 66
# of unresolved testcases 28
# of unsupported tests 116
=== objc Summary ===
# of expected passes 1035
# of expected failures 6
=== libjava Summary ===
# of expected passes 2022
# of unexpected failures 25
# of expected failures 18
# of untested testcases 28
=== libstdc++-v3 Summary ===
# of expected passes 405
# of unexpected failures 4
# of unexpected successes 1
# of expected failures 25
And, my build 1:3.2.2ds4-0pre5 says:
=== g++ Summary ===
# of expected passes 7326
# of unexpected failures 7
# of unexpected successes 1
# of expected failures 88
# of untested testcases 23
# of unsupported tests 6
=== g77 Summary ===
# of expected passes 1418
# of unexpected failures 17
# of unresolved testcases 14
# of untested testcases 3
# of unsupported tests 8
=== gcc Summary ===
# of expected passes 18353
# of unexpected failures 80
# of expected failures 66
# of unresolved testcases 33
# of unsupported tests 117
=== objc Summary ===
# of expected passes 1035
# of expected failures 6
=== libjava Summary ===
# of expected passes 2014
# of unexpected failures 29
# of expected failures 18
# of untested testcases 32
=== libstdc++-v3 Summary ===
# of expected passes 220
# of unexpected failures 129
# of expected failures 5
We should be careful to read this result is not complete build, it's
on the way. But the result seems good. I don't know why it becomes
OK, but Bug#175526 can reassign to gcc-3.2, and it can be fixed if the
latest gcc-3.2 build itself. I still wait my build to judge (=
reassign to gcc-3.2) that it's really right or not.
Regards,
-- gotom
Reply to: