From: Guillaume Le Vaillant <glv@posteo.net>
To: Joeke <joeke@posteo.net>
Cc: 57348-done@debbugs.gnu.org
Subject: bug#57348: [PATCH] gnu: Add eisl
Date: Sat, 03 Sep 2022 14:03:27 +0000 [thread overview]
Message-ID: <87wnaklfd9.fsf@kitej> (raw)
In-Reply-To: <87h71sd3gd.fsf@kitej>
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
I updated your patch for version 2.62 which has the fixes for the
libraries. I also added a 'wrap' phase, so calling "(compile-file ...)"
should work without having to propagate gcc-toolchain etc.
Patch pushed as 5cf9b98d1cdd25ee44224f8256ea6f719b9aa0bd.
Thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2022-09-03 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 22:58 [bug#57348] [PATCH] gnu: Add eisl Joeke
2022-08-27 11:07 ` Guillaume Le Vaillant
2022-08-30 19:38 ` Joeke
2022-08-31 11:58 ` Guillaume Le Vaillant
2022-09-03 14:03 ` Guillaume Le Vaillant [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnaklfd9.fsf@kitej \
--to=glv@posteo.net \
--cc=57348-done@debbugs.gnu.org \
--cc=joeke@posteo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).