unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Ekaitz Zarraga <ekaitz@elenq.tech>,
	55833@debbugs.gnu.org, othacehe@gnu.org
Subject: bug#55833: cross-base error: wrong type argument in position 1
Date: Tue, 07 Jun 2022 20:33:58 +0200	[thread overview]
Message-ID: <eb961bdb61d352de2771a188441c5ded8364da96.camel@telenet.be> (raw)
In-Reply-To: <5qR8o5eSldiy3chXSPnE2qn1NtHm4FklEGx9APhm0xFagHrv8fZapayVEMvdtJ4Kqw6vTwbyu3rCyPc38oEbJq78X2XW7RwWoe3DzND_K_w=@elenq.tech>

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

Ekaitz Zarraga schreef op di 07-06-2022 om 15:43 [+0000]:
> I think the error was introduced in the commit b55310603f0df7d5ae02d47cb8d4be58bf1d41ca but I can't really explain what's happening.

I guess it's due to the introduction of

  lookup-platform-by-target-or-system

Proposed solution:

  * rename platform-linux-architecture to
    '%platform-linux-architecture'
    and define a wrapper 'platform-linux-architecture' displaying
    a proper error message ‘unsupported target’ or such.

and

  * use "riscv64-linux-gnu" instead of "riscv64-unknown-linux-gnu"
    (as expected by (guix platforms riscv)).

Greetings,
Maxime.

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

  reply	other threads:[~2022-06-07 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:43 bug#55833: cross-base error: wrong type argument in position 1 Ekaitz Zarraga
2022-06-07 18:33 ` Maxime Devos [this message]
2022-06-08 10:35   ` Josselin Poiret via Bug reports for GNU Guix
2022-06-08 13:06     ` Maxime Devos
2022-06-08 13:12     ` Maxime Devos
2022-06-08 16:29   ` Ekaitz Zarraga
2022-06-08 17:11     ` Ekaitz Zarraga

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=eb961bdb61d352de2771a188441c5ded8364da96.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55833@debbugs.gnu.org \
    --cc=ekaitz@elenq.tech \
    --cc=othacehe@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 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).