<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Linux] determineArchitecture is not cross-compile aware"
href="https://bugs.webkit.org/show_bug.cgi?id=169886#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Linux] determineArchitecture is not cross-compile aware"
href="https://bugs.webkit.org/show_bug.cgi?id=169886">bug 169886</a>
from <span class="vcard"><a class="email" href="mailto:clopez@igalia.com" title="Carlos Alberto Lopez Perez <clopez@igalia.com>"> <span class="fn">Carlos Alberto Lopez Perez</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=169886#c1">comment #1</a>)
<span class="quote">> Does build-webkit have any options to set separate host/target architectures
> for cross compiling?
>
> I have not investigated it, but I would be surprised if build-webkit (or
> build-jsc) was intended for use in cross-compiling. I would have instructed
> users to use CMake directly instead. If you're cross-compiling you most
> likely want a production build rather than a development build, after all.</span >
The intent is to run buildbots that cross-build. All WebKit buildbots build webkit with the script build-webkit (or build-jsc if they only build JSC).
And some architectures are not really powerful, having to build webkit natively on those its beyond reasonable. So the only solution that remains is cross-build.
The current JSCOnly ARM bots <a href="http://build.webkit.org/waterfall?category=misc">http://build.webkit.org/waterfall?category=misc</a> are currently cross-building, and we are setting up a MIPS bot for JSCOnly also (initially). I'm not sure if they are not hitting this issue (ENABLE_FTL_JIT=ON is passed in the cmakeargs because hostOS==amd64) because the hostOS is a 32-bit one (i686) in their case, or for some other workaround that I missed.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>