From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Cross-compiling Guile 2.0
Date: Sun, 20 Mar 2011 14:50:43 +0100 [thread overview]
Message-ID: <87mxkp2958.fsf@gnu.org> (raw)
In-Reply-To: <m3tyezweut.fsf@unquote.localdomain> (Andy Wingo's message of "Sat, 19 Mar 2011 12:04:42 +0100")
Hello!
Andy Wingo <wingo@pobox.com> writes:
> It's true that a simple command-line argument and fluid could work, but
> the situation will get more complicated, so we will need some part of
> Guile to define the host and target triplets. That's the questions I
> was really asking: where in Guile to define those?
There’s already ‘%host-type’. However, I don’t think defining
‘%target-type’ would make sense since:
1. Of the GNU triplet, only the $target_arch matters for bytecode;
2. You can really choose at run-time what target you want to build
for, by just setting the endianness fluid.
Now, if we want to produce something comparable to cross-GCC &
cross-Binutils[*], we could install, say, arm-linux-gnueabi-guile-tools
in addition to guile-tools; the former would somehow set the right
endianness for that target when running ‘arm-linux-gnueabi-guile-tools
compile’.
WDYT?
Thanks,
Ludo’.
[*] Installed cross-GCC and cross-Binutils provide binaries called
TARGET-gcc, TARGET-ld, etc.
next prev parent reply other threads:[~2011-03-20 13:50 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
2011-03-18 10:17 ` Ludovic Courtès
2011-03-19 11:04 ` Andy Wingo
2011-03-20 13:50 ` Ludovic Courtès [this message]
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=87mxkp2958.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).