Bug 14744
Summary: | Cross-compilation broken by recent pcre change | ||
---|---|---|---|
Product: | WebKit | Reporter: | Koen Kooi <koen> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | barraclough, zecke |
Priority: | P2 | ||
Version: | 523.x (Safari 3) | ||
Hardware: | Mac | ||
OS: | OS X 10.4 |
Koen Kooi
It looks like r24411 introduced running the just built 'dftables', which of course doesn't work when crosscompiling x86->arm, since my opteron chokes on armv5te instructions.
The error
echo "#include <string.h>" > /data/build/koen/OE/build/tmp/angstrom/work/armv5te-angstrom-linux-gnueabi/webkit-0.0+svn20070724-r1/WebKitBuilds/Debug//WebCore/tmp/DocTypeStrings.cpp && gperf -CEot -L ANSI-C -k '*' -N findDoctypeEntry -F ,PubIDInfo::eAlmostStandards,PubIDInfo::eAlmostStandards < /data/build/koen/OE/build/tmp/angstrom/work/armv5te-angstrom-linux-gnueabi/webkit-0.0+svn20070724-r1/WebCore/html/DocTypeStrings.gperf >> /data/build/koen/OE/build/tmp/angstrom/work/armv5te-angstrom-linux-gnueabi/webkit-0.0+svn20070724-r1/WebKitBuilds/Debug//WebCore/tmp/DocTypeStrings.cpp/data/build/koen/OE/build/tmp/angstrom/work/armv5te-angstrom-linux-gnueabi/webkit-0.0+svn20070724-r1/WebKitBuilds/Debug/JavaScriptCore/pcre/tmp/dftables tmp/chartables.c/data/build/koen/OE/build/tmp/angstrom/work/armv5te-angstrom-linux-gnueabi/webkit-0.0+svn20070724-r1/WebKitBuilds/Debug/JavaScriptCore/pcre/tmp/dftables: /data/build/koen/OE/build/tmp/angstrom/work/armv5te-angstrom-linux-gnueabi/webkit-0.0+svn20070724-r1/WebKitBuilds/Debug/JavaScriptCore/pcre/tmp/dftables: cannot execute binary filemake[1]: *** [tmp/chartables.c] Error 126
Could this be changes to run an external dftables (e.g. dftables from x86 pcre) or back out the offending cset?
WebkitGdk did work brilliantly on my arm devices before this cset.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Koen Kooi
As I said in the starting comment:
"WebkitGdk did work brilliantly on my arm devices before this cset."
So tagging it with 'QT' is useless
Koen Kooi
I worked around this with:
--- packages/webkit/webkit/WebKit.pro 63fd1bd947de2d3abe6a011685e6173bf0a804e1
+++ packages/webkit/webkit/WebKit.pro c4db9377c267835f4ec934a4d53207e26c25b99c
@@ -1,9 +1,8 @@ SUBDIRS += \
TEMPLATE = subdirs
CONFIG += ordered
!gdk-port:CONFIG += qt-port
qt-port:SUBDIRS += WebKitQt/Plugins
SUBDIRS += \
- JavaScriptCore/pcre/dftables.pro \
WebCore \
JavaScriptCore/kjs/testkjs.pro
and doing
cd ${S}/JavaScriptCore/pcre
${BUILD_CC} dftables.c -o dftables -I. -I../wtf
cp dftables ${S}/WebKitBuilds/Debug/JavaScriptCore/pcre/tmp/
before starting (q)make
David Kilzer (:ddkilzer)
Is this still an issue? See also Bug 16818.
Gavin Barraclough
We no longer use PCRE, I don't believe this bug can still be live.