From: Danny Milosavljevic <dannym@scratchpost.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: Mathieu Othacehe <m.othacehe@gmail.com>, 29296@debbugs.gnu.org
Subject: [bug#29296] [PATCH 2/2] gexp: Add 'let-system'.
Date: Sat, 23 May 2020 00:44:34 +0200 [thread overview]
Message-ID: <20200523004434.059d1960@scratchpost.org> (raw)
In-Reply-To: <87mv3mk2ql.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Hi Ludo,
maybe a little off-topic, but why do I have to use the following patch on
armhf-linux (*not* cross compiling) in order to stop it from pulling in
i686-cross-gcc?
Makes no sense to me at all...
diff --git a/gnu/packages/mes.scm b/gnu/packages/mes.scm
index 347aef0..524b8e8 100644
--- a/gnu/packages/mes.scm
+++ b/gnu/packages/mes.scm
@@ -120,8 +120,9 @@ extensive examples, including parsers for the Javascript and C99 languages.")
((string-prefix? "x86_64-linux" target-system)
;; Use cross-compiler rather than #:system "i686-linux" to get
;; MesCC 64 bit .go files installed ready for use with Guile.
- `(("i686-linux-binutils" ,(cross-binutils "i686-unknown-linux-gnu"))
- ("i686-linux-gcc" ,(cross-gcc "i686-unknown-linux-gnu"))))
+ `( ;("i686-linux-binutils" ,(cross-binutils "i686-unknown-linux-gnu"))
+ ;("i686-linux-gcc" ,(cross-gcc "i686-unknown-linux-gnu"))
+))
(else
'())))
("graphviz" ,graphviz)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-22 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 16:18 [bug#29296] [PATCH 0/2] gexp: Add 'let-system' Ludovic Courtès
2017-11-14 16:25 ` [bug#29296] [PATCH 1/2] gexp: Compilers can now return lowerable objects Ludovic Courtès
2017-11-14 16:25 ` [bug#29296] [PATCH 2/2] gexp: Add 'let-system' Ludovic Courtès
2017-11-15 11:27 ` Mathieu Othacehe
2017-11-16 9:10 ` Ludovic Courtès
2020-05-22 22:44 ` Danny Milosavljevic [this message]
2020-05-22 23:01 ` Marius Bakke
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=20200523004434.059d1960@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=29296@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=m.othacehe@gmail.com \
/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).