From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1798 invoked by alias); 11 Jun 2014 14:59:35 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 1781 invoked by uid 89); 11 Jun 2014 14:59:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout24.012.net.il Received: from mtaout24.012.net.il (HELO mtaout24.012.net.il) (80.179.55.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Jun 2014 14:59:32 +0000 Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0N7000600EMA5800@mtaout24.012.net.il> for gdb-patches@sourceware.org; Wed, 11 Jun 2014 17:55:39 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N70006LIESQKU00@mtaout24.012.net.il>; Wed, 11 Jun 2014 17:55:39 +0300 (IDT) Date: Wed, 11 Jun 2014 14:59:00 -0000 From: Eli Zaretskii Subject: Re: Building the current snapshot on Windows with Guile In-reply-to: <87ha3rocq3.fsf@gnu.org> To: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Cc: xdje42@gmail.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83k38nze3y.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8BIT References: <83y4x614y6.fsf@gnu.org> <87ha3rocq3.fsf@gnu.org> X-IsSubscribed: yes X-SW-Source: 2014-06/txt/msg00450.txt.bz2 > From: ludo@gnu.org (Ludovic Courtès) > Cc: Eli Zaretskii , "gdb-patches\@sourceware.org" > Date: Wed, 11 Jun 2014 14:24:52 +0200 > > Doug Evans skribis: > > > (*1): As Ludo suggested, we could compile these files during a gdb > > build, but that doesn't work in a cross-compilation scenario (without > > requiring more complexity in the build, which would be nice to avoid). > > Are these files guaranteed to be equivalent across configurations (I'm > > guessing not), and if not does guile provide a cross-compiler for them > > (I'm guessing not - could be wrong of course)? > > It does provide a cross-compiler (info "(guile) Compilation"): > > guix compile --target=mips64el-linux-gnu foo.scm -o foo.go > > But note that the interpretation of triplets might defer from that of > GDB. In particular, for platforms that support several ABIs with > different word sizes, it recognizes some specific triplet > extensions–e.g., “mips64el-linux-gnuabi64” for the N64 ABI on MIPS. See > . Apart of the issue with multi-ABI platforms, are there any other reasons for the *.go files to be non-portable? E.g., if they were compiled on a 64-bit Windows 7, will they work on a 32-bit Windows XP? Does the answer depend on whether the Guile executable that compiled the *.scm files was a 64-bit or a 32-bit executable? What about compiling on GNU/Linux and using on Windows, when the CPU is the same or from the same family?