unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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: Sun, 20 Mar 2011 16:25:02 +0100	[thread overview]
Message-ID: <m38vw9vmpd.fsf@unquote.localdomain> (raw)
In-Reply-To: <87mxkp2958.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 20 Mar 2011 14:50:43 +0100")

Hi :)

On Sun 20 Mar 2011 14:50, ludo@gnu.org (Ludovic Courtès) writes:

> There’s already ‘%host-type’.

Ah, cool.

> 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.

Can I convince you otherwise?  Right now it's endianness, but I would
like to hack an ARM native compiler sometime soonish, and that's going
to be easier as a cross-compiler; and at that point you do need the
%target-type.

I guess that's my point: right now it's endianness, in the future it
will be more things, might as well go ahead and add %target-type now.

> Now, if we want to produce something comparable to cross-GCC &
> cross-Binutils[*], we could install, say, arm-linux-gnueabi-guile-tools

Yes, that sounds good, though I would be happier if we did this simply
with --program-prefix and --target.

I really don't want to add an endianness kwarg to `compile', for
example, though an endianness fluid in (language assembly) is OK for
me.

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-03-20 15:25 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
2011-03-20 15:25           ` Andy Wingo [this message]
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=m38vw9vmpd.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).