From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Felix Lechner via" <help-guix@gnu.org>
Subject: Re: make clean-go breaks my build environment
Date: Wed, 02 Nov 2022 04:02:31 -0400 [thread overview]
Message-ID: <3180503b-f3ed-46f9-aaca-fd1a1441a986@app.fastmail.com> (raw)
In-Reply-To: <20221102024803.GB13985@dismail.de>
On Wed, Nov 2, 2022, at 3:48 AM, jgart wrote:
> On Wed, 02 Nov 2022 08:20:09 +0100 Ricardo Wurmus <rekado@elephly.net> wrote:
>>
>> 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”?
>
> I mean that instead of getting a quick build now that the guile object
> files are gone it just gets stuck indefinitely at that warning.
Try `make clean-go && make && echo hooray`. My guess is that your build is finishing successfully (`make` exits with status 0) and the last output just happens to be those warning messages.
If by “gets […] stuck” you mean that `make` never exits, that would indeed be a problem.
This is legitimately confusing, though! A good reason to figure out how not to trigger those warnings.
next prev parent reply other threads:[~2022-11-02 8:04 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
2022-11-02 7:48 ` jgart
2022-11-02 8:02 ` Philip McGrath [this message]
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=3180503b-f3ed-46f9-aaca-fd1a1441a986@app.fastmail.com \
--to=philip@philipmcgrath.com \
--cc=help-guix@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.
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).