From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126361 invoked by alias); 9 Feb 2016 10:41:55 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 126341 invoked by uid 89); 9 Feb 2016 10:41:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=HTo:U*libffi-discuss, HContent-Transfer-Encoding:8bit X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 09 Feb 2016 10:41:54 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id ED4D6C0C2376; Tue, 9 Feb 2016 10:41:52 +0000 (UTC) Received: from zebedee.pink ([10.3.113.3]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u19Afpxm025091; Tue, 9 Feb 2016 05:41:52 -0500 Subject: Re: Cross-compiling libffi on ppc 603e To: =?UTF-8?B?RnLDqWTDqXJpYw==?= , libffi-discuss@sourceware.org References: <20160203112152.6e7bfb4c@gbiloba.org> <20160209090223.340b3bc0@gbiloba.org> From: Andrew Haley Message-ID: <56B9C26F.3070601@redhat.com> Date: Tue, 09 Feb 2016 10:41:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160209090223.340b3bc0@gbiloba.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2016/txt/msg00004.txt.bz2 On 09/02/16 08:02, Frédéric wrote: >> > Any idea why I can't cross-compile on this platform? I can see that ppc >> > 32bits is supported. I may need to give an additional env. var. to my >> > toolchain? > No idea? Look for where FFI_LONG_LONG_MAX is defined. Check that it is correct. Patch if necessary. Send us the patch. Thanks, Andrew.