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: Mon, 30 May 2011 22:22:38 +0200	[thread overview]
Message-ID: <m3k4d8ndkh.fsf@unquote.localdomain> (raw)
In-Reply-To: <m3aae5ped1.fsf@unquote.localdomain> (Andy Wingo's message of "Sun, 29 May 2011 20:10:18 +0200")

On Sun 29 May 2011 20:10, Andy Wingo <wingo@pobox.com> writes:

> On Fri 27 May 2011 16:51, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Sounds good, but you’d need additional data that maps triplets (well,
>> $host_cpu) to low-level info such as endianness and word size, right?
>
> Yes, which caused me a bit of agony on Friday after writing that mail.
> Not resolved yet.  Durnit!

In the end I decided to punt.  I added a stub (system base target)
module and wired it up to the compiler, but didn't implement the
endianness / word-size database.  Patches accepted :)

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-05-30 20:22 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
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 [this message]
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=m3k4d8ndkh.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).