From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Dealing with cross-compilation
Date: Tue, 31 Mar 2009 12:04:36 -0700 [thread overview]
Message-ID: <m3fxgto6nv.fsf@pobox.com> (raw)
In-Reply-To: <873actn05f.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Tue, 31 Mar 2009 18:10:36 +0200")
Hi,
On Tue 31 Mar 2009 09:10, ludo@gnu.org (Ludovic Courtès) writes:
> Greg Troxel <gdt@ir.bbn.com> writes:
>
>> So, building guile probably needs either to build guile as a host tool
>>
>> if host != target, preferably in an objdir, and then that can be used.
>>
>> take a --with-guile that points to a working host guile, and people
>> doing cross builds will have to build guile first.
>
> Right, we could use an already installed Guile 1.8/1.9 when
> cross-compiling. That means we have to make sure the compiler can run
> on top of 1.8. I think this is currently the case. Andy?
The compiler won't work on 1.8, I don't think. But you could install a
1.9 on the host, and that would work -- modulo some endianness issues
that would need to be sorted out for a host guilec to be able to
cross-compile to the target.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2009-03-31 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 17:08 Guile 1.8 success on `i386-apple-darwin9.6.0' Ludovic Courtès
2009-03-26 18:34 ` Ludovic Courtès
2009-03-26 21:10 ` Neil Jerram
2009-03-26 21:36 ` Ludovic Courtès
2009-03-26 22:21 ` Neil Jerram
2009-03-27 8:58 ` Ludovic Courtès
2009-03-27 20:14 ` Neil Jerram
2009-03-27 13:48 ` Greg Troxel
2009-03-27 14:54 ` Ludovic Courtès
2009-03-27 18:34 ` Greg Troxel
2009-03-31 16:10 ` Dealing with cross-compilation Ludovic Courtès
2009-03-31 19:04 ` Andy Wingo [this message]
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=m3fxgto6nv.fsf@pobox.com \
--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).