all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 26926@debbugs.gnu.org
Subject: bug#26926: [PATCH] gnu: update Mes to 0.6.
Date: Wed, 17 May 2017 09:32:05 +0200	[thread overview]
Message-ID: <8760h02b2i.fsf@gnu.org> (raw)
In-Reply-To: <8760h05vx2.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 16 May 2017 23:33:29 +0200")

Heya,

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> What I call Mescc is a Scheme program that can be executed (interpreted)
> by Mes, but it can also be run by Guile.  Like so:
>
>     guix package -i nyacc mes
>     guile -c '(use-modules (language c99 compiler)) (with-input-from-string "int main () {return printf (\"Hi Mescc\n\");}" c99-input->elf)' > a.out
>     chmod +x a.out
>     ./a.out
>
>        => Hi Mescc
>
> Does this make it more explicit?

Yes, thanks!  It looks very exciting.

>>> +         ,@(if (or (equal? (%current-system) "x86_64-linux")
>>> +                   (equal? (%current-target-system) "x86_64-linux"))
>>
>> Note that %current-system is a “system type” like “x86_64-linux”
>> whereas %current-target-system is a GNU triplet like
>> “x86_64-linux-pc-gnu”.  Thus, the second line should be
>>
>>   (string-prefix? (%current-target-system) "x86_64-linux")
>
> Ah...ok.  As an aside: would we want to to change one of these names?

You mean like renaming ‘%current-target-system’ to
‘%current-target-triplet’ for example?  Why not, it would probably help
avoid this confusion.

>> Please read ‘HACKING’ for the details.  Before pushing, can you reply to
>> this message and sign your reply with the OpenPGP key that you’ll use
>> to sign commits?  Also please upload your OpenPGP key to Savannah.
>
> Okay, great!

Awesome, that was long overdue.

Thank you!

Ludo’.

      reply	other threads:[~2017-05-17  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 16:11 bug#26926: [PATCH] gnu: update Mes to 0.6 Jan Nieuwenhuizen
2017-05-16 20:06 ` Ludovic Courtès
2017-05-16 21:33   ` Jan Nieuwenhuizen
2017-05-17  7:32     ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760h02b2i.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26926@debbugs.gnu.org \
    --cc=janneke@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.