Bug 393495 – net-libs/webkit-gtk-1.6.1-r301 - Source/WebCore/bindings/js/SerializedScriptValue.cpp:510:5: internal compiler error: in simplify_gen_subreg_concatn, at lower-subreg .c:468

• Status: RESOLVED NEEDINFO
• Product: Gentoo Linux

[Description Bernhard Nägele 2011-12-07 10:22:10 UTC]

The build process stops after some time with the following message:

make[1]: Leaving directory `/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/work/webkit-1.6.1'
make: *** [all] Fehler 2
 * ERROR: net-libs/webkit-gtk-1.6.1-r301 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of 'emerge --info =net-libs/webkit-gtk-1.6.1-r301',
 * the complete build log and the output of 'emerge -pqv =net-libs/webkit-gtk-1.6.1-r301'.
 * The complete build log is located at '/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/temp/environment'.
 * S: '/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/work/webkit-1.6.1'

[Comment 1 Dustin Polke 2011-12-07 11:06:21 UTC]

(In reply to comment #0)
> The build process stops after some time with the following message:
> 
> make[1]: Leaving directory
> `/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/work/webkit-1.6.1'
> make: *** [all] Fehler 2
>  * ERROR: net-libs/webkit-gtk-1.6.1-r301 failed (compile phase):
>  *   emake failed
>  * 
>  * If you need support, post the output of 'emerge --info
> =net-libs/webkit-gtk-1.6.1-r301',
>  * the complete build log and the output of 'emerge -pqv
> =net-libs/webkit-gtk-1.6.1-r301'.
>  * The complete build log is located at
> '/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/temp/environment'.
>  * S: '/var/tmp/portage/net-libs/webkit-gtk-1.6.1-r301/work/webkit-1.6.1'

This message is not useful. Please post your emerge --info and attach the full build.log.
Thanks.

[Comment 2 Bernhard Nägele 2011-12-07 11:16:58 UTC]

Created attachment 295063 [details]
end of build.log

Sorry, I wanted originaly to attach the build.log, but it was too big to upload.
Here is the split part if it.

[Comment 3 Bernhard Nägele 2011-12-07 11:19:20 UTC]

Created attachment 295065 [details]
emerge --info output

And here is the emerge-info output.....

[Comment 4 Jeroen Roovers (RETIRED) 2011-12-07 13:24:14 UTC]

Comment on attachment 295063 [details]
end of build.log

(In reply to comment #2)
> Created attachment 295063 [details]
> end of build.log
> 
> Sorry, I wanted originaly to attach the build.log, but it was too big to
> upload.
> Here is the split part if it.

Compress it first.

[Comment 5 Bernhard Nägele 2011-12-07 21:57:24 UTC]

Created attachment 295133 [details]
build.log compressed

[Comment 6 Pacho Ramos 2011-12-08 17:40:58 UTC]

I cannot reproduce, maybe it's arm specific. Are you able to compile 1.6.1-r300? When -r301 fails, does it always fail in the same way? Have you tried to recompile it with MAKEOPTS="-j1"?

[Comment 7 Bernhard Nägele 2011-12-10 08:52:31 UTC]

The failure with compilation the -r301 happens also with compiler setting -j1.
I will attach another build.log afterwards.

[Comment 8 Bernhard Nägele 2011-12-10 09:02:45 UTC]

Created attachment 295341 [details]
build.log compressed with -j1 compiler option

[Comment 9 Pacho Ramos 2011-12-10 18:55:26 UTC]

(In reply to comment #6)
> I cannot reproduce, maybe it's arm specific. Are you able to compile
> 1.6.1-r300? When -r301 fails, does it always fail in the same way? 

And what about the other questions ;) ^

[Comment 10 Pacho Ramos 2012-01-30 11:13:23 UTC]

(In reply to comment #9)
> (In reply to comment #6)
> > I cannot reproduce, maybe it's arm specific. Are you able to compile
> > 1.6.1-r300? When -r301 fails, does it always fail in the same way? 
> 
> And what about the other questions ;) ^