From: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix package path
Date: Tue, 20 Dec 2022 22:38:58 +0100 [thread overview]
Message-ID: <87edstoivh.fsf@yahoo.com.br> (raw)
In-Reply-To: <87pmcfzjgc.fsf@yahoo.com.br> (Antonio Carlos Padoan Junior's message of "Mon, 19 Dec 2022 13:06:27 +0100")
Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br> writes:
Hi,
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).
There is something missing in the environment when channel
is called from a local directory (using -L argument). I think that perhaps
"specification->package" does not work correctly, but this pure
speculation.
From this point in the channel's definition, all other
packages are not recognized when using "guix build -L ...".
I moved the gtklp package to the end of the file and all other packages
compiled (sbcl-lispiec as well).
I'm not sure this is a bug. But well, I think important to mention
anyway.
Best regards,
--
Antonio Carlos PADOAN JUNIOR
GPG fingerprint:
243F 237F 2DD3 4DCA 4EA3 1341 2481 90F9 B421 A6C9
next prev parent reply other threads:[~2022-12-20 21:40 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 [this message]
2022-12-21 22:42 ` Ludovic Courtès
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=87edstoivh.fsf@yahoo.com.br \
--to=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).