On Fri, Feb 9, 2018 at 12:00 PM, Emilio Cobos Álvarez <emi...@crisal.io> wrote:
> On 02/09/2018 10:49 AM, Henri Sivonen wrote:
>> Is there some trick to make gkrust compilation succeed on a 32-bit system?
> The BSD folks seem to be using --disable-debug-symbols for that, see
Thanks. Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1436981 .
(gkrust completed. libxul linking still ahead. Building with -j 1
isn't very fast...)
On Fri, Feb 9, 2018 at 1:31 PM, Ted Mielczarek <t...@mielczarek.org> wrote:
There seems to be a step that involves running code within the chroot
environment to set thing up. I take it that to target armv7, the host
would then need to be aarch64 and not x86_64? Or maybe one could run
mach bootstrap on a real ARMv7 system and then dump the file system to
an external disk and move that over?
Anyway, considering how complicated this is, it would be great to have
try server targets for ARMv7+NEON GNU/Linux and aarch64 GNU/Linux for
testing stuff in a hopefully Android-representative way when using
actual Android looks even messier. (Running gtest microbenchmarks on
hardware that, unlike phones, has stable clock speed under
single-threaded 100% load but hopefully is close enough to phones in
terms of core design to be representative.)
dev-platform mailing list