unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
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:35:26 -0500	[thread overview]
Message-ID: <20221105103526.GB25795@dismail.de> (raw)
In-Reply-To: <CO4GNHWEI9S2.2S4GNZPLB7UHW@guix-framework>

On Sat, 05 Nov 2022 15:17:47 +0000 "(" <paren@disroot.org> wrote:
> On Sat Nov 5, 2022 at 3:16 PM GMT, jgart wrote:
> > I'm just wondering if I'm missing a step after running `make clean-go`
> > in order to then get the speed up again.
> 
> I don't think you are.
> 
>     -- (

So, just build a few times and it should speed up because the go files have been regenerated?

For example, after running `make clean-go` building nnn which is a small
file manager takes the following:

 time ./pre-inst-env guix build nnn
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'

/gnu/store/byap6zn0g5gbv43wg67cdkvlnl24hhlg-nnn-4.6

real    3m43.164s
user    5m8.290s
sys     0m0.734s

If I run that same command I expect it to be faster because I assume
that the go files are already there but lo and behold:

 time ./pre-inst-env guix build nnn
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'

/gnu/store/byap6zn0g5gbv43wg67cdkvlnl24hhlg-nnn-4.6

real    3m43.498s
user    5m6.128s
sys     0m0.683s

And here I try it one more time:

time ./pre-inst-env guix build nnn
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'

/gnu/store/byap6zn0g5gbv43wg67cdkvlnl24hhlg-nnn-4.6

real    3m36.902s
user    5m1.588s
sys     0m0.671s

fun times ;()

wdyt


  reply	other threads:[~2022-11-05 15:36 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 [this message]
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=20221105103526.GB25795@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).