From: jgart <jgart@dismail.de>
To: "(" <paren@disroot.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, help-guix@gnu.org
Subject: Re: make clean-go breaks my build environment
Date: Sat, 5 Nov 2022 10:55:37 -0500 [thread overview]
Message-ID: <20221105105537.GB29058@dismail.de> (raw)
In-Reply-To: <CO4H2S36VMIQ.1EG7F8ECIMHVF@guix-framework>
On Sat, 05 Nov 2022 15:37:45 +0000 "(" <paren@disroot.org> wrote:
> Ahh. I thought you were talking about using ``make -j$(nproc)''. Use that and it should get
> a LOT faster.
ah that was the missing step I was talking about.
communication over email can be hard sometimes
Should we document that running make is required after running make clean-go?
I don't think a new user will deduce that especially if they're new to guile
and don't know what go is or how it relate to whatever running make is doing...
They might make the same error I just made.
prev parent reply other threads:[~2022-11-05 15:56 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
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 [this message]
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=20221105105537.GB29058@dismail.de \
--to=jgart@dismail.de \
--cc=help-guix@gnu.org \
--cc=paren@disroot.org \
--cc=rekado@elephly.net \
/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).