From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Cross-compiling Guile 2.0
Date: Fri, 18 Mar 2011 01:04:46 +0100 [thread overview]
Message-ID: <m3y64dxpi9.fsf@unquote.localdomain> (raw)
In-Reply-To: <87k4gb99uv.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 06 Mar 2011 23:12:40 +0100")
On Sun 06 Mar 2011 23:12, ludo@gnu.org (Ludovic Courtès) writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> In principle, how should Guile 2.0 be cross-compiled? I'm thinking
>> mostly of the part of the build that compiles all the installed modules.
>
> Guile 2.0 can only be cross-compiled when the endianness and word size
> of the host and target match (because the bytecode generation cannot be
> parameterized by these.)
You know, I think it's actually just endianness right now; I don't see
where word size comes into it, except for the cookie.
Anyway, in the future when we do AOT compilation, this question will be
more serious. (I would like to do AOT stuff this year.) So, following
the autoconf manual ("Specifying Target Triplets"), we would have build
== host, but target == the arm triple; so we would need
`target-endianness' (and possibly `target-word-size') in the compiler.
Where do you think we should put these, given that you don't want them
in (rnrs bytevectors)? :-)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-18 0:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 19:47 Cross-compiling Guile 2.0 Neil Jerram
2011-03-05 21:41 ` Andy Wingo
2011-03-06 11:03 ` Neil Jerram
2011-03-06 20:43 ` Andy Wingo
2011-03-06 22:12 ` Ludovic Courtès
2011-03-18 0:04 ` Andy Wingo [this message]
2011-03-18 10:17 ` Ludovic Courtès
2011-03-19 11:04 ` Andy Wingo
2011-03-20 13:50 ` Ludovic Courtès
2011-03-20 15:25 ` Andy Wingo
2011-03-20 21:31 ` Ludovic Courtès
2011-03-20 21:53 ` Andy Wingo
2011-03-21 19:58 ` Ludovic Courtès
2011-03-21 20:42 ` Andy Wingo
2011-05-27 14:32 ` Andy Wingo
2011-05-27 14:51 ` Ludovic Courtès
2011-05-29 18:10 ` Andy Wingo
2011-05-30 20:22 ` Andy Wingo
2011-05-31 15:24 ` Ludovic Courtès
2011-03-16 13:02 ` Jan Nieuwenhuizen
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y64dxpi9.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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).