From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42491) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dAtSF-0007Qg-Ob for guix-patches@gnu.org; Wed, 17 May 2017 03:33:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dAtSA-0007cy-R6 for guix-patches@gnu.org; Wed, 17 May 2017 03:33:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:46819) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dAtSA-0007c3-Nv for guix-patches@gnu.org; Wed, 17 May 2017 03:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dAtSA-0008QB-IP for guix-patches@gnu.org; Wed, 17 May 2017 03:33:02 -0400 Subject: bug#26926: [PATCH] gnu: update Mes to 0.6. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <87inl3770q.fsf@gnu.org> <87k25g5zyi.fsf@gnu.org> <8760h05vx2.fsf@gnu.org> Date: Wed, 17 May 2017 09:32:05 +0200 In-Reply-To: <8760h05vx2.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 16 May 2017 23:33:29 +0200") Message-ID: <8760h02b2i.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Jan Nieuwenhuizen Cc: 26926@debbugs.gnu.org Heya, Jan Nieuwenhuizen 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-stri= ng "int main () {return printf (\"Hi Mescc\n\");}" c99-input->elf)' > a.out > chmod +x a.out > ./a.out > > =3D> 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 =E2=80=9Csystem type=E2=80=9D like =E2=80= =9Cx86_64-linux=E2=80=9D >> whereas %current-target-system is a GNU triplet like >> =E2=80=9Cx86_64-linux-pc-gnu=E2=80=9D. 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 =E2=80=98%current-target-system=E2=80=99 to =E2=80=98%current-target-triplet=E2=80=99 for example? Why not, it would p= robably help avoid this confusion. >> Please read =E2=80=98HACKING=E2=80=99 for the details. Before pushing, = can you reply to >> this message and sign your reply with the OpenPGP key that you=E2=80=99l= l use >> to sign commits? Also please upload your OpenPGP key to Savannah. > > Okay, great! Awesome, that was long overdue. Thank you! Ludo=E2=80=99.