From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: xdje42@gmail.com, gdb-patches@sourceware.org
Subject: Re: Building the current snapshot on Windows with Guile
Date: Thu, 12 Jun 2014 08:27:00 -0000 [thread overview]
Message-ID: <87ha3qlehr.fsf@gnu.org> (raw)
In-Reply-To: <83k38nze3y.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 11 Jun 2014 17:59:29 +0300")
Eli Zaretskii <eliz@gnu.org> skribis:
>> From: ludo@gnu.org (Ludovic Courtès)
>> Cc: Eli Zaretskii <eliz@gnu.org>, "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
>> Date: Wed, 11 Jun 2014 14:24:52 +0200
>>
>> Doug Evans <xdje42@gmail.com> 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
>> <http://git.savannah.gnu.org/cgit/guile.git/tree/module/system/base/target.scm#n76>.
>
> Apart of the issue with multi-ABI platforms, are there any other
> reasons for the *.go files to be non-portable?
In Guile 2.0, .go files are not portable essentially because sizeof(SCM)
is the size of a pointer, and because numbers stored in .go files are in
native endianness. (Guile 2.2 uses ELF as its container format, with
similar issues.)
> E.g., if they were compiled on a 64-bit Windows 7, will they work on a
> 32-bit Windows XP?
No.
> Does the answer depend on whether the Guile executable that compiled
> the *.scm files was a 64-bit or a 32-bit executable?
No.
> What about compiling on GNU/Linux and using on Windows, when the CPU
> is the same or from the same family?
That works fine.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-06-12 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 15:24 Eli Zaretskii
2014-06-09 15:39 ` Joel Brobecker
2014-06-09 17:30 ` Eli Zaretskii
2014-06-14 18:01 ` Eli Zaretskii
2014-06-09 21:04 ` Ludovic Courtès
2014-06-10 19:55 ` Doug Evans
2014-06-10 20:26 ` Eli Zaretskii
2014-06-11 12:24 ` Ludovic Courtès
2014-06-11 14:59 ` Eli Zaretskii
2014-06-12 8:27 ` Ludovic Courtès [this message]
2014-06-12 17:15 ` Eli Zaretskii
2014-06-12 19:46 ` Ludovic Courtès
2014-06-12 19:58 ` Eli Zaretskii
2014-06-13 8:35 ` Ludovic Courtès
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=87ha3qlehr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).