From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Cross-compilation from armhf to mips64el
Date: Fri, 09 Oct 2015 10:33:26 +0200
Message-ID: <874mi0tp9l.fsf@gnu.org>
References: <20151005190838.GA5006@debian> <87pp0rbx28.fsf@gnu.org>
	<20151008184814.GA3800@debian> <87egh4ookh.fsf@netris.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47626)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ZkT7N-0001tz-8u
	for guix-devel@gnu.org; Fri, 09 Oct 2015 04:33:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ZkT7J-000054-5j
	for guix-devel@gnu.org; Fri, 09 Oct 2015 04:33:33 -0400
In-Reply-To: <87egh4ookh.fsf@netris.org> (Mark H. Weaver's message of "Thu, 08
	Oct 2015 20:47:26 -0400")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org

Mark H Weaver <mhw@netris.org> skribis:

> Andreas Enge <andreas@enge.fr> writes:
>
>> Hm, I do not understand your message.
>>
>> On Tue, Oct 06, 2015 at 09:45:35PM +0200, Ludovic Court=C3=A8s wrote:
>>> The problem in question is this:
>>> ...
>>> Long story short: everything is alright.  :-)
>>
>> So is there a problem or not? The function in question is supposed to
>> prevent cross-compilation from 32 to 64 bits;
>
> mips64el-linux-gnu uses 32-bit pointers, which is most likely the
> important issue.  Note that we successfully cross-compile from i686 to
> mips64el-linux-gnu, so I guess that works.
>
> I would prefer not to disable these builds until we understand what's
> going on.  Maybe it would be easy to fix.

Could be.  I guess an issue is that nobody tries to build an
ARM=C2=A0=E2=86=92=C2=A0mips64el cross-toolchain.

Ludo=E2=80=99.