From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id E10857ED1D for ; Wed, 14 Oct 2015 17:19:25 +0200 (CEST) IronPort-PHdr: 9a23:4RbR3xTEC9AsYCMYNEizHZNy2Npsv+yvbD5Q0YIujvd0So/mwa64YxON2/xhgRfzUJnB7Loc0qyN4/ymCTNLscrJmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3BPAZ4bt74BpTVx5zukbvip9uDPE4Y2HKUWvBbElaflU3prM4YgI9veO4a6yDihT92QdlQ3n5iPlmJnhzxtY+a9Z9n9DlM6bp6r5YTGY2zRakzTKRZATI6KCh1oZSz7ViQBTeIs0AAX2sflFJoDgzB4Qv/V5H3+n/hqudz0S+yIc37F7U9Qiiv9bwtRBK+2wkdMDts2W3Ni8F2xIRSrB+770h2z5TVbYe9Mv1ifeXaZ9xMFjkJZdpYSyEUWtD0VIAIFedUeL8A94Q= Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=adrien@notk.org; spf=PermError smtp.mailfrom=adrien@notk.org; spf=None smtp.helo=postmaster@nautica.notk.org Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: PermError (mail3-smtp-sop.national.inria.fr: cannot correctly interpret sender authenticity information from domain of adrien@notk.org) identity=mailfrom; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BfAgCNcR5W/5NHeVtegya6RYQhAQ2BWoMTggp/AoFDOBQBAQEBAQEBAYEJgh+CCAEBBCNWEAsYAgIFEw4CAg8FGDGIRa9nk0EBAQEHAgEfgSKFVIR+hQ0HgmkxgRQFhzqHBIdXjRMIWpswHwEBQoQEPIciAQEB X-IPAS-Result: A0BfAgCNcR5W/5NHeVtegya6RYQhAQ2BWoMTggp/AoFDOBQBAQEBAQEBAYEJgh+CCAEBBCNWEAsYAgIFEw4CAg8FGDGIRa9nk0EBAQEHAgEfgSKFVIR+hQ0HgmkxgRQFhzqHBIdXjRMIWpswHwEBQoQEPIciAQEB X-IronPort-AV: E=Sophos;i="5.17,681,1437429600"; d="scan'208";a="150546085" Received: from nautica.notk.org ([91.121.71.147]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-GCM-SHA384; 14 Oct 2015 17:19:25 +0200 Received: by nautica.notk.org (Postfix, from userid 1003) id 52475C009; Wed, 14 Oct 2015 17:19:24 +0200 (CEST) Date: Wed, 14 Oct 2015 17:19:24 +0200 From: Adrien Nader To: Stefan Hellermann Cc: Pierre Chambart , caml-list@inria.fr Message-ID: <20151014151924.GA6386@notk.org> References: <561CFDBE.5090708@ocamlpro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] Application crashing when build with cross-compiler 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