From: Ricardo Wurmus <rekado@elephly.net>
To: jgart <jgart@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: make clean-go breaks my build environment
Date: Wed, 02 Nov 2022 08:20:09 +0100 [thread overview]
Message-ID: <87y1stakkw.fsf@elephly.net> (raw)
In-Reply-To: <20221101205322.GB15546@dismail.de>
jgart <jgart@dismail.de> writes:
> after running `make clean-go` the build gets consistently stuck on
> this message:
>
> WARNING: Use of `load' in declarative module (guix ui). Add #:declarative? #f to your define-module invocation.
> WARNING: (guix build python-build-system): imported module (guix build utils) overrides core binding `delete'
These are warnings, not errors. What do you mean by “gets […] stuck”?
“make clean-go” is only supposed to delete .go files.
--
Ricardo
next prev parent reply other threads:[~2022-11-02 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 1:53 make clean-go breaks my build environment jgart
2022-11-02 7:20 ` Ricardo Wurmus [this message]
2022-11-02 7:48 ` jgart
2022-11-02 8:02 ` Philip McGrath
2022-11-02 9:15 ` Csepp
2022-11-04 0:45 ` jgart
2022-11-04 16:16 ` (
2022-11-05 15:16 ` jgart
2022-11-05 15:17 ` (
2022-11-05 15:35 ` jgart
2022-11-05 15:37 ` (
2022-11-05 15:55 ` jgart
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=87y1stakkw.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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.
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).