From: Adrien Nader <adrien@notk.org>
To: Stefan Hellermann <stefan@the2masters.de>
Cc: Pierre Chambart <pierre.chambart@ocamlpro.com>, caml-list@inria.fr
Subject: Re: [Caml-list] <DKIM> Application crashing when build with cross-compiler
Date: Wed, 14 Oct 2015 17:19:24 +0200 [thread overview]
Message-ID: <20151014151924.GA6386@notk.org> (raw)
In-Reply-To: <CAANYUdBFY2AQ1k_gpXibNAHcXgqYBgObae+=MfruTZUja_9sBA@mail.gmail.com>
On Wed, Oct 14, 2015, Stefan Hellermann wrote:
> I tried to reproduce this on a x86_32 cross-compiled target, but failed. I
> tried to create exactly the same environment for x86_32, same libc, same
> compiler, same kernel. Only difference to compiling for my target is
> endianess, mips is big endian and x86_32 is little endian.
>
> Should I try to descripe how to setup Qemu for an mips target and build
> OCaml and unison with a cross-compiler?
>
> Is there anything else I can try? Can someone point me to a few test
> scripts which I could run on the mips target and see if something fails?
Hmmmm, endianess is indeed likely to cause troubles.
Do the cross-build from x86_64 to ix86 (or the other way round) and
look for warnings from as (need the end of the build iirc). It will
point you to lines that result from assumptions about word size and,
quite likely, endianness. I have no idea if they will be the ones that
cause you troubles but they're worth checking I believe.
Unfortunately I don't know the code emission well enough to be more
precise about its requirements.
As for the qemu approach, it's something not to neglect because it's
easy to setup and gives results.
--
Adrien Nader
next prev parent reply other threads:[~2015-10-14 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 11:50 [Caml-list] " Stefan Hellermann
[not found] ` <561CFDBE.5090708@ocamlpro.com>
2015-10-14 12:29 ` [Caml-list] <DKIM> " Stefan Hellermann
2015-10-14 15:19 ` Adrien Nader [this message]
2015-10-14 15:59 ` Xavier Leroy
2015-10-14 20:10 ` Adrien Nader
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151014151924.GA6386@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=pierre.chambart@ocamlpro.com \
--cc=stefan@the2masters.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox