* Re: [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 19:57 [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error" Grant
@ 2012-01-31 19:45 ` Todd Goodman
2012-01-31 20:36 ` Grant
2012-01-31 21:37 ` [gentoo-user] " walt
2012-02-05 3:11 ` Grant
2 siblings, 1 reply; 13+ messages in thread
From: Todd Goodman @ 2012-01-31 19:45 UTC (permalink / raw
To: gentoo-user
* Grant <emailgrant@gmail.com> [120131 14:26]:
> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
> failed at the exact same point both times. The build log doesn't
> mention a segfault. Does anyone know how to fix this? I was able to
> compile gcc-4.3.3 a short while ago.
>
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
> In function 'internal_dfa_insn_code':
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
> internal compiler error: Aborted
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.gentoo.org/> for instructions.
> make[3]: *** [insn-attrtab.o] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
> make: *** [bootstrap-lean] Error 2
> emake failed
>
> - Grant
Did you check the log for OOM (Out of Memory) problems?
I've had problems building gcc on a machine with limited RAM when my swap
hasn't been enabled.
Todd
^ permalink raw reply [flat|nested] 13+ messages in thread
* [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error"
@ 2012-01-31 19:57 Grant
2012-01-31 19:45 ` Todd Goodman
` (2 more replies)
0 siblings, 3 replies; 13+ messages in thread
From: Grant @ 2012-01-31 19:57 UTC (permalink / raw
To: Gentoo mailing list
I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
failed at the exact same point both times. The build log doesn't
mention a segfault. Does anyone know how to fix this? I was able to
compile gcc-4.3.3 a short while ago.
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
In function 'internal_dfa_insn_code':
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.
make[3]: *** [insn-attrtab.o] Error 1
make[3]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 19:45 ` Todd Goodman
@ 2012-01-31 20:36 ` Grant
2012-01-31 21:24 ` Jarry
0 siblings, 1 reply; 13+ messages in thread
From: Grant @ 2012-01-31 20:36 UTC (permalink / raw
To: gentoo-user
>> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
>> failed at the exact same point both times. The build log doesn't
>> mention a segfault. Does anyone know how to fix this? I was able to
>> compile gcc-4.3.3 a short while ago.
>>
>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
>> In function 'internal_dfa_insn_code':
>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
>> internal compiler error: Aborted
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <http://bugs.gentoo.org/> for instructions.
>> make[3]: *** [insn-attrtab.o] Error 1
>> make[3]: Leaving directory
>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
>> make[2]: *** [all-stage2-gcc] Error 2
>> make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>> make[1]: *** [stage2-bubble] Error 2
>> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>> make: *** [bootstrap-lean] Error 2
>> emake failed
>>
>> - Grant
>
> Did you check the log for OOM (Out of Memory) problems?
>
> I've had problems building gcc on a machine with limited RAM when my swap
> hasn't been enabled.
>
> Todd
I just checked but there is nothing like that in the logs.
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 20:36 ` Grant
@ 2012-01-31 21:24 ` Jarry
2012-01-31 22:16 ` Grant
0 siblings, 1 reply; 13+ messages in thread
From: Jarry @ 2012-01-31 21:24 UTC (permalink / raw
To: gentoo-user
On 31-Jan-12 21:36, Grant wrote:
>>> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
>>> failed at the exact same point both times. The build log doesn't
>>> mention a segfault. Does anyone know how to fix this? I was able to
>>> compile gcc-4.3.3 a short while ago.
>>>
>>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
>>> In function 'internal_dfa_insn_code':
>>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
>>> internal compiler error: Aborted
>>> Please submit a full bug report,
>>> with preprocessed source if appropriate.
>>> See<http://bugs.gentoo.org/> for instructions.
>>> make[3]: *** [insn-attrtab.o] Error 1
>>> make[3]: Leaving directory
>>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
>>> make[2]: *** [all-stage2-gcc] Error 2
>>> make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>>> make[1]: *** [stage2-bubble] Error 2
>>> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>>> make: *** [bootstrap-lean] Error 2
>>> emake failed
>>>
>>> - Grant
>>
>> Did you check the log for OOM (Out of Memory) problems?
>>
>> I've had problems building gcc on a machine with limited RAM when my swap
>> hasn't been enabled.
>>
>> Todd
>
> I just checked but there is nothing like that in the logs.
>
> - Grant
Some versions of GCC I was able to compile with MAKEOPTS="-j1"
only. Whenever I have set it to higher number, it simply failed
with similar error. Surprising, other versions I could compile
even with "-j4"...
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 19:57 [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error" Grant
2012-01-31 19:45 ` Todd Goodman
@ 2012-01-31 21:37 ` walt
2012-01-31 22:54 ` Peter Humphrey
2012-01-31 23:17 ` wdk@moriah
2012-02-05 3:11 ` Grant
2 siblings, 2 replies; 13+ messages in thread
From: walt @ 2012-01-31 21:37 UTC (permalink / raw
To: gentoo-user
On 01/31/2012 11:57 AM, Grant wrote:
> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
> failed at the exact same point both times. The build log doesn't
> mention a segfault. Does anyone know how to fix this? I was able to
> compile gcc-4.3.3 a short while ago.
Are you using the new 4.3.3 to build 4.5.3? The gcc package actually
compiles gcc twice, once with your existing compiler and again with
the new compiler itself (at least it worked that way in the old days).
I'm wondering if the internal compiler error occurs during the first
build (using 4.3.3) or the second (using 4.5.3).
Not that I'd know what to do with that info except to answer my own
question :)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 21:24 ` Jarry
@ 2012-01-31 22:16 ` Grant
0 siblings, 0 replies; 13+ messages in thread
From: Grant @ 2012-01-31 22:16 UTC (permalink / raw
To: gentoo-user
>>>> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
>>>> failed at the exact same point both times. The build log doesn't
>>>> mention a segfault. Does anyone know how to fix this? I was able to
>>>> compile gcc-4.3.3 a short while ago.
>>>>
>>>>
>>>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
>>>> In function 'internal_dfa_insn_code':
>>>>
>>>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
>>>> internal compiler error: Aborted
>>>> Please submit a full bug report,
>>>> with preprocessed source if appropriate.
>>>> See<http://bugs.gentoo.org/> for instructions.
>>>> make[3]: *** [insn-attrtab.o] Error 1
>>>> make[3]: Leaving directory
>>>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
>>>> make[2]: *** [all-stage2-gcc] Error 2
>>>> make[2]: Leaving directory
>>>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>>>> make[1]: *** [stage2-bubble] Error 2
>>>> make[1]: Leaving directory
>>>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>>>> make: *** [bootstrap-lean] Error 2
>>>> emake failed
>>>>
>>>> - Grant
>>>
>>>
>>> Did you check the log for OOM (Out of Memory) problems?
>>>
>>> I've had problems building gcc on a machine with limited RAM when my
>>> swap
>>> hasn't been enabled.
>>>
>>> Todd
>>
>>
>> I just checked but there is nothing like that in the logs.
>>
>> - Grant
>
>
> Some versions of GCC I was able to compile with MAKEOPTS="-j1"
> only. Whenever I have set it to higher number, it simply failed
> with similar error. Surprising, other versions I could compile
> even with "-j4"...
That can't be it, I set MAKEOPTS="-j1" on all my systems years ago. :)
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 21:37 ` [gentoo-user] " walt
@ 2012-01-31 22:54 ` Peter Humphrey
2012-02-01 21:06 ` Grant
2012-01-31 23:17 ` wdk@moriah
1 sibling, 1 reply; 13+ messages in thread
From: Peter Humphrey @ 2012-01-31 22:54 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
On Tuesday 31 January 2012 21:37:34 walt wrote:
> The gcc package actually compiles gcc twice, once with your existing
> compiler and again with the new compiler itself (at least it worked that
> way in the old days).
I believe it's three times now: the first time with the old compiler, then
with the new one, then again with the second new one. Then the last two are
compared; they should be the same.
I forget where I read that though.
--
Rgds
Peter Linux Counter 5290, 1994-04-23
[-- Attachment #2: Type: text/html, Size: 2867 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 21:37 ` [gentoo-user] " walt
2012-01-31 22:54 ` Peter Humphrey
@ 2012-01-31 23:17 ` wdk@moriah
1 sibling, 0 replies; 13+ messages in thread
From: wdk@moriah @ 2012-01-31 23:17 UTC (permalink / raw
To: gentoo-user@lists.gentoo.org; +Cc: gentoo-user@lists.gentoo.org
Check USE/C flags, there may have been changes between versions (I think this happened to me) Try compiling without any of them and if it works start looking for the bad one.
W.Kenworthy
On 01/02/2012, at 5:37, walt <w41ter@gmail.com> wrote:
> On 01/31/2012 11:57 AM, Grant wrote:
>> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
>> failed at the exact same point both times. The build log doesn't
>> mention a segfault. Does anyone know how to fix this? I was able to
>> compile gcc-4.3.3 a short while ago.
>
> Are you using the new 4.3.3 to build 4.5.3? The gcc package actually
> compiles gcc twice, once with your existing compiler and again with
> the new compiler itself (at least it worked that way in the old days).
>
> I'm wondering if the internal compiler error occurs during the first
> build (using 4.3.3) or the second (using 4.5.3).
>
> Not that I'd know what to do with that info except to answer my own
> question :)
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 22:54 ` Peter Humphrey
@ 2012-02-01 21:06 ` Grant
2012-02-01 22:54 ` walt
0 siblings, 1 reply; 13+ messages in thread
From: Grant @ 2012-02-01 21:06 UTC (permalink / raw
To: gentoo-user
>> The gcc package actually compiles gcc twice, once with your existing
>
>> compiler and again with the new compiler itself (at least it worked that
>
>> way in the old days).
>
>
>
> I believe it's three times now: the first time with the old compiler, then
> with the new one, then again with the second new one. Then the last two are
> compared; they should be the same.
I do get this when emerging gcc-4.3.4:
* Your x86 arch is not supported.
* Hope you know what you are doing. Hardened will not work.
I wonder if it could be related. 4.3.4 compiles fine.
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
* [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-02-01 21:06 ` Grant
@ 2012-02-01 22:54 ` walt
2012-02-01 23:30 ` Grant
0 siblings, 1 reply; 13+ messages in thread
From: walt @ 2012-02-01 22:54 UTC (permalink / raw
To: gentoo-user
On 02/01/2012 01:06 PM, Grant wrote:
> I do get this when emerging gcc-4.3.4:
>
> * Your x86 arch is not supported.
> * Hope you know what you are doing. Hardened will not work.
Are you upgrading from a non-hardened system?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-02-01 22:54 ` walt
@ 2012-02-01 23:30 ` Grant
0 siblings, 0 replies; 13+ messages in thread
From: Grant @ 2012-02-01 23:30 UTC (permalink / raw
To: gentoo-user
>> I do get this when emerging gcc-4.3.4:
>>
>> * Your x86 arch is not supported.
>> * Hope you know what you are doing. Hardened will not work.
>
> Are you upgrading from a non-hardened system?
Nope, just upgrading gcc on a system that's always been hardened.
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
* [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-01-31 19:57 [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error" Grant
2012-01-31 19:45 ` Todd Goodman
2012-01-31 21:37 ` [gentoo-user] " walt
@ 2012-02-05 3:11 ` Grant
2012-02-07 4:52 ` Grant
2 siblings, 1 reply; 13+ messages in thread
From: Grant @ 2012-02-05 3:11 UTC (permalink / raw
To: Gentoo mailing list
> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
> failed at the exact same point both times. The build log doesn't
> mention a segfault. Does anyone know how to fix this? I was able to
> compile gcc-4.3.3 a short while ago.
>
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
> In function 'internal_dfa_insn_code':
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
> internal compiler error: Aborted
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.gentoo.org/> for instructions.
> make[3]: *** [insn-attrtab.o] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
> make: *** [bootstrap-lean] Error 2
> emake failed
>
> - Grant
I get the same error trying to recompile gcc-4.3.4 which is currently
installed and was emerged successfully about a week ago. I'll file a
bug?
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
* [gentoo-user] Re: gcc-4.5.3-r1 fails to compile with "internal compiler error"
2012-02-05 3:11 ` Grant
@ 2012-02-07 4:52 ` Grant
0 siblings, 0 replies; 13+ messages in thread
From: Grant @ 2012-02-07 4:52 UTC (permalink / raw
To: Gentoo mailing list
>> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it
>> failed at the exact same point both times. The build log doesn't
>> mention a segfault. Does anyone know how to fix this? I was able to
>> compile gcc-4.3.3 a short while ago.
>>
>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
>> In function 'internal_dfa_insn_code':
>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
>> internal compiler error: Aborted
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <http://bugs.gentoo.org/> for instructions.
>> make[3]: *** [insn-attrtab.o] Error 1
>> make[3]: Leaving directory
>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
>> make[2]: *** [all-stage2-gcc] Error 2
>> make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>> make[1]: *** [stage2-bubble] Error 2
>> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
>> make: *** [bootstrap-lean] Error 2
>> emake failed
>>
>> - Grant
>
> I get the same error trying to recompile gcc-4.3.4 which is currently
> installed and was emerged successfully about a week ago. I'll file a
> bug?
>
> - Grant
Fixed! It may have been changing my locale from POSIX to UTF8 or
maybe some kernel changes I made.
- Grant
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2012-02-07 4:54 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-31 19:57 [gentoo-user] gcc-4.5.3-r1 fails to compile with "internal compiler error" Grant
2012-01-31 19:45 ` Todd Goodman
2012-01-31 20:36 ` Grant
2012-01-31 21:24 ` Jarry
2012-01-31 22:16 ` Grant
2012-01-31 21:37 ` [gentoo-user] " walt
2012-01-31 22:54 ` Peter Humphrey
2012-02-01 21:06 ` Grant
2012-02-01 22:54 ` walt
2012-02-01 23:30 ` Grant
2012-01-31 23:17 ` wdk@moriah
2012-02-05 3:11 ` Grant
2012-02-07 4:52 ` Grant
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox