From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Cross-compiling Guile 2.0
Date: Sat, 05 Mar 2011 22:41:57 +0100 [thread overview]
Message-ID: <m3mxl9ckii.fsf@unquote.localdomain> (raw)
In-Reply-To: <87hbbhbb99.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 05 Mar 2011 19:47:14 +0000")
On Sat 05 Mar 2011 20:47, 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.
I have never cross-compiled anything, so I really don't know.
Ideally we could make a cross-compiling Guile that executed on the host,
but produced .go files for the target.
Hummmmmm. Does that mean that for cross-compile builds, that we should
not add the $builddir to the LOAD_COMPILED_PATH? Probably so, right? A
cross-compiler probably doesn't autocompile either. So then the
cross-compiler receives as its inputs the source files from a project,
then produces .go files for the target, but does not load .go files from
the target.
Does that sound right to you?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-05 21:41 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 [this message]
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
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=m3mxl9ckii.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).