From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 66537@debbugs.gnu.org, Hiep Pham <hiepph9@proton.me>,
guix-patches@gnu.org
Subject: bug#66537: configure: error: The Guile bindings of GnuTLS are missing
Date: Fri, 08 Dec 2023 16:50:09 +0100 [thread overview]
Message-ID: <87bkb08zim.fsf_-_@gmail.com> (raw)
In-Reply-To: <87fs0o5p7g.fsf@gmail.com> (Simon Tournier's message of "Wed, 29 Nov 2023 20:33:55 +0100")
Hi Ludo,
On Wed, 29 Nov 2023 at 20:33, Simon Tournier <zimon.toutoune@gmail.com> wrote:
> On mer., 22 nov. 2023 at 13:05, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> @example
>> -guix shell -D guix --pure
>> +guix shell -D guix -CPW
>> @end example
>>
>> or even, from within a Git worktree for Guix:
>>
>> @example
>> -guix shell --pure
>> +guix shell -CPW
>> @end example
>
> I would not recommend that or adding also the option -N. Else, the
> development experience can be annoying.
As said, I disagree with this change pushed by
01361d46b8e0481ad56665d7a06c276b08f59c6d.
Could you revert? Because as explained by…
> For instance, “make check” will probably fail because some substitutes
> are missing (see #67532 [1], e.g., tests/derivations.scm).
…the option ’-CPW’ is not a solution. Other said, it would require in
addition ’-N’.
To me, this recommendation of container is like a bazooka for chasing
the real bug: about why --pure does not clean all as expected. Or why
“guile” is found elsewhere?
Cheers,
simon
next prev parent reply other threads:[~2023-12-08 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 12:49 bug#66537: configure: error: The Guile bindings of GnuTLS are missing Hiep Pham via Bug reports for GNU Guix
2023-10-17 8:59 ` Daniel Meißner via Bug reports for GNU Guix
2023-10-17 10:28 ` Hiep Pham via Bug reports for GNU Guix
2023-11-22 12:05 ` bug#66537: [PATCH] doc: Recommend building in ‘guix shell -CPW’ Ludovic Courtès
2023-11-29 19:33 ` Simon Tournier
2023-12-08 15:50 ` Simon Tournier [this message]
2023-12-19 9:30 ` Simon Tournier
2023-12-04 21:51 ` bug#67366: " Ludovic Courtès
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=87bkb08zim.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=66537@debbugs.gnu.org \
--cc=guix-patches@gnu.org \
--cc=hiepph9@proton.me \
--cc=ludo@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 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.