all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: raingloom <raingloom@riseup.net>, Xinglu Chen <public@yoctocell.xyz>
Cc: 46124@debbugs.gnu.org
Subject: [bug#46124] [PATCH] Idris 2
Date: Mon, 26 Apr 2021 23:27:39 +0200	[thread overview]
Message-ID: <5003aa160dc82b35b06e60d425a09309199e1670.camel@telenet.be> (raw)
In-Reply-To: <20210426172240.683c4c2b@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

raingloom schreef op ma 26-04-2021 om 17:22 [+0200]:
> There hasn't been a tagged release since then, so I'm sending my
> original patch, but I should note that in my channel I've been tracking
> the latest commit, which does seem to work, although it's been a while
> since I used Idris for anything complicated.
> 
> +                     ;; TODO detect toolchain
> +                     "CC=gcc")))

Unless idris has a compiler built in that uses gcc for compiling
idris to machine code, this should likely be
,(string-append "CC=" (cc-for-target)) instead, such that the
cross-compiler is used when cross-compiling.

Teaching (cc-for-target) to detect which toolchain should be used
is a separate matter.  Maybe it could be a macro that looks at
(package-native-inputs this-package) or something.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-04-26 21:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  5:43 [bug#46124] [PATCH] Idris 2 raingloom
     [not found] ` <87r1j267c6.fsf@yoctocell.xyz>
2021-04-26 15:22   ` raingloom
2021-04-26 21:27     ` Maxime Devos [this message]
2021-04-29 18:43       ` raingloom
2021-04-30  8:24         ` Xinglu Chen
2021-05-03  2:10           ` raingloom
2021-05-04 17:12             ` Xinglu Chen
2021-05-11 21:47               ` raingloom
2021-05-14 12:08                 ` Xinglu Chen
2021-04-30  8:50         ` Maxime Devos

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=5003aa160dc82b35b06e60d425a09309199e1670.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=46124@debbugs.gnu.org \
    --cc=public@yoctocell.xyz \
    --cc=raingloom@riseup.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 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.