unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>
Cc: zimoun <zimon.toutoune@gmail.com>,  guix-devel <guix-devel@gnu.org>
Subject: Re: guix package path
Date: Wed, 21 Dec 2022 23:42:31 +0100	[thread overview]
Message-ID: <87len02xbc.fsf@gnu.org> (raw)
In-Reply-To: <87edstoivh.fsf@yahoo.com.br> (Antonio Carlos Padoan Junior's message of "Tue, 20 Dec 2022 22:38:58 +0100")

Hi,

Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br> skribis:

> I would like to give some feedback concerning this issue I faced.
> I found an offending package definition in my channel (but the issue is only
> present when using -L argument):
>
> (define-public gtklp
>   (let ((toolchain (specification->package "clang-toolchain@10")))
>     (package-with-c-toolchain gtklp-bad-tool `(("toolchain" ,toolchain)))))
>
> For instance, when using "guix build -L ... gtklp", the alternative toolchain did not
> get called and compilation fails because of that (toolchain must be clang-toolchain@10).

We don’t have enough info to be sure, but could it be that there are two
‘gtklp’ packages in your package collection, for instance because
‘gtklp-bad-tool’ is also public?  ‘specification->package’ prints a
warning if it’s ambiguous.

HTH,
Ludo’.


  reply	other threads:[~2022-12-21 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wn6nzx2g.fsf.ref@yahoo.com.br>
2022-12-19  7:12 ` guix package path Antonio Carlos Padoan Junior
2022-12-19 10:47   ` zimoun
2022-12-19 12:06     ` Antonio Carlos Padoan Junior
2022-12-19 14:35       ` zimoun
2022-12-20 21:38       ` Antonio Carlos Padoan Junior
2022-12-21 22:42         ` Ludovic Courtès [this message]
2022-12-30 14:57           ` zimoun

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=87len02xbc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=acpadoanjr@yahoo.com.br \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@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).