1 |
On Monday 15 October 2007 09:30:52 am Stuart Howard wrote: |
2 |
> As part of regular updates I have come across an error with gcc, the |
3 |
> system is ~x86. |
4 |
> The error has been occurring for a week or so and my usual wait till |
5 |
> it goes away approach does not seem to be working. Originally the |
6 |
> error was called against a file with reference to fortran so I changed |
7 |
> the use flag to - but no help as the result is as below. |
8 |
> |
9 |
> If someone has a suggestion for a way forward I would appreciate it. |
10 |
> |
11 |
> stu |
12 |
> |
13 |
> |
14 |
> |
15 |
> |
16 |
> |
17 |
> /var/tmp/portage/sys-devel/gcc-4.2.2/work/gcc-4.2.2/gcc/expmed.c: In |
18 |
> function 'expa nd_divmod': |
19 |
> /var/tmp/portage/sys-devel/gcc-4.2.2/work/gcc-4.2.2/gcc/expmed.c:4933: |
20 |
> internal com piler error: in free_list, at lists.c:66 |
21 |
> Please submit a full bug report, |
22 |
> with preprocessed source if appropriate. |
23 |
> See <URL:http://bugs.gentoo.org/> for instructions. |
24 |
> The bug is not reproducible, so it is likely a hardware or OS problem. |
25 |
> make[3]: *** [expmed.o] Error 1 |
26 |
> make[3]: Leaving directory |
27 |
> `/var/tmp/portage/sys-devel/gcc-4.2.2/work/build/gcc' make[2]: *** |
28 |
> [all-stageprofile-gcc] Error 2 |
29 |
> make[2]: Leaving directory |
30 |
> `/var/tmp/portage/sys-devel/gcc-4.2.2/work/build' make[1]: *** |
31 |
> [stageprofile-bubble] Error 2 |
32 |
> make[1]: Leaving directory |
33 |
> `/var/tmp/portage/sys-devel/gcc-4.2.2/work/build' make: *** |
34 |
> [profiledbootstrap] Error 2 |
35 |
> * |
36 |
> * ERROR: sys-devel/gcc-4.2.2 failed. |
37 |
> * Call stack: |
38 |
> * ebuild.sh, line 1695: Called dyn_compile |
39 |
> * ebuild.sh, line 1033: Called qa_call 'src_compile' |
40 |
> * ebuild.sh, line 44: Called src_compile |
41 |
> * ebuild.sh, line 1377: Called toolchain_src_compile |
42 |
> * toolchain.eclass, line 26: Called gcc_src_compile |
43 |
> * toolchain.eclass, line 1546: Called gcc_do_make |
44 |
> * toolchain.eclass, line 1420: Called die |
45 |
> * The specific snippet of code: |
46 |
> * emake \ |
47 |
> * LDFLAGS="${LDFLAGS}" \ |
48 |
> * STAGE1_CFLAGS="${STAGE1_CFLAGS}" \ |
49 |
> * LIBPATH="${LIBPATH}" \ |
50 |
> * BOOT_CFLAGS="${BOOT_CFLAGS}" \ |
51 |
> * ${GCC_MAKE_TARGET} \ |
52 |
> * || die "emake failed with ${GCC_MAKE_TARGET}" |
53 |
> * The die message: |
54 |
> * emake failed with profiledbootstrap |
55 |
> * |
56 |
> * If you need support, post the topmost build error, and the call |
57 |
> stack if relevan t. |
58 |
> * A complete build log is located at |
59 |
> '/var/log/portage/sys-devel:gcc-4.2.2:2007101 5-101943.log'. |
60 |
|
61 |
Hey Stu, |
62 |
|
63 |
I just upgraded three gentoo boxes using gcc-4.2.2. No issues, aside from a |
64 |
few packages that refuse to compile. |
65 |
|
66 |
What I would recommend is some basic maintenance... Sorry, but is it possible |
67 |
you are seeing heat related issues? Perhaps memory errors? |
68 |
|
69 |
It could be a good time to let memtest exercise your mems... |
70 |
|
71 |
|
72 |
|
73 |
|
74 |
-- |
75 |
|
76 |
|
77 |
From the Desk of: Jerome D. McBride |
78 |
-- |
79 |
gentoo-user@g.o mailing list |