Bug 137686
| Summary: | [GTK] undefined method `[]' for nil:NilClass (NoMethodError) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alberto Garcia <berto> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Alberto Garcia
I just saw WebKitGTK+ 2.6.1 failing to build in ppc64el:
[ 2%] Generating ../../DerivedSources/JavaScriptCore/LLIntDesiredOffsets.h
cd /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-powerpc64le-linux-gnu/Source/JavaScriptCore && /usr/bin/ruby /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-powerpc64le-linux-gnu/DerivedSources/JavaScriptCore/ /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/JavaScriptCore/llint/LowLevelInterpreter.asm /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-powerpc64le-linux-gnu/DerivedSources/JavaScriptCore/LLIntDesiredOffsets.h
/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/JavaScriptCore/offlineasm/parser.rb:64:in `processIncludeOptions': undefined method `[]' for nil:NilClass (NoMethodError)
from /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb:37:in `<main>'
make[3]: *** [DerivedSources/JavaScriptCore/LLIntDesiredOffsets.h] Error 1
Source/JavaScriptCore/CMakeFiles/LLIntOffsetsExtractor.dir/build.make:78: recipe for target 'DerivedSources/JavaScriptCore/LLIntDesiredOffsets.h' failed
make[3]: Leaving directory '/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-powerpc64le-linux-gnu'
make[2]: *** [Source/JavaScriptCore/CMakeFiles/LLIntOffsetsExtractor.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
Full build log here (NOTE: 1.5MB text document):
https://buildd.debian.org/status/fetch.php?pkg=webkit2gtk&arch=ppc64el&ver=2.6.1%2Bdfsg1-1&stamp=1413237439
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alberto Garcia
It built fine after a second try. I haven't taken a look at this yet, but I guess this might be some sort of race condition?
Alberto Garcia
We haven't been able to reproduce it again after many attempts in different architectures, it was probably fixed in 2.6.2, I'll close this.