Bug 35639 - [Qt] mmap inside javascriptcore fails if building an app on os x >= 10.5 and deploying it onto 10.4
Summary: [Qt] mmap inside javascriptcore fails if building an app on os x >= 10.5 and ...
Status: RESOLVED DUPLICATE of bug 34888
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2010-03-03 03:22 PST by Tor Arne Vestbø
Modified: 2010-03-10 04:55 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tor Arne Vestbø 2010-03-03 03:22:50 PST
This bug report originated from issue QTBUG-7065
http://bugreports.qt.nokia.com/browse/QTBUG-7065

--- Description ---

10% of my customers are still with os x 10.4!<br/>
Starting from Qt 4.6 mmaps are failing inside JavaScriptCore when I deploy an application using QtScript compiled on OS X 10.6 onto 10.4.<br/>
I tracked down the issue to a platform detection mistake inside src/3rdparty/javascriptcore/JavaScriptCore/wtf/Platform.h:

<p>.... about line 40 ...<br/>
...</p>

<p>The following small fix makes it work for me:</p>

<p>...<br/>
...</p>

<p>Also it should say "BUILDING_FOR_TIGER" instead of "BUILD_ON_TIGER" for the sake of clarity.<br/>
PS: Thanks for having that flag to disable JIT. QtScript works just great for me!</p>

--- Comments ---

We're aware of this issue (see http://www.pubbs.net/webkit/200909/85716).
Recently some macros were added to wtf/Platform.h, including TARGETING_TIGER ( = your BUILDING_FOR_TIGER).
I think the correct fix would be to use those defines in wtf/VMTags.h (replacing BUILDING_ON_TIGER).
But it needs to be fixed upstream (http://bugs.webkit.org).
Comment 1 Tor Arne Vestbø 2010-03-10 04:55:34 PST

*** This bug has been marked as a duplicate of bug 34888 ***