From: Oleg Pykhalov <go.wigust@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5
Date: Tue, 03 Oct 2017 12:16:58 +0300 [thread overview]
Message-ID: <87o9po8ub9.fsf@gmail.com> (raw)
In-Reply-To: <87h8vlslg9.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 29 Sep 2017 09:06:46 -0400")
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> Efraim Flashner <efraim@flashner.co.il> writes:
>>
>>> On Fri, Sep 29, 2017 at 07:21:27PM +0800, Huang, Ying wrote:
[...]
>>> you're in need of a 'make clean'. If you don't want to have to rebuild
>>> everything, then 'rm -- gnu/*go gnu/s*/*go gnu/tests/*go' should take
>>> care of all of the affected modules.
>
> For the reference, there already is a "clean-go" target that
> accomplishes just that, so you could run "make clean-go" the next time
> you are faced with a similar error.
A bit of info from my experience writing cgit-service-type and 'cgit test':
$ rm gnu/services/version-control.go gnu/services/web.go rm -f gnu/*.go gnu/s*/*g.o
Even `make clean-go' in guix checkout directory didn't help. So, random
thought did the job:
$ for x in $(find ~/.cache/ -type f -name '*.go' | grep test); do rm $x; done
next prev parent reply other threads:[~2017-10-03 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 11:21 gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5 Huang, Ying
2017-09-29 11:53 ` Andy Wingo
2017-09-29 12:09 ` Huang, Ying
2017-09-29 11:58 ` Efraim Flashner
2017-09-29 12:10 ` Huang, Ying
2017-09-29 13:06 ` Maxim Cournoyer
2017-10-03 9:16 ` Oleg Pykhalov [this message]
2017-10-04 13:50 ` Maxim Cournoyer
2017-10-05 0:00 ` Oleg Pykhalov
2017-10-06 17:07 ` Oleg Pykhalov
2017-10-07 1:10 ` Maxim Cournoyer
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=87o9po8ub9.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.