From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] build: pull: Compile .scm files in one process.
Date: Fri, 27 Nov 2015 11:07:35 +0100 [thread overview]
Message-ID: <87bnafbvrs.fsf@gnu.org> (raw)
In-Reply-To: <87fuzrlt6f.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Fri, 27 Nov 2015 09:53:28 +0100")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> ?: 2 [primitive-load "/gnu/store/d51z2xkwp1vh0dh6gqadyyzv21m0b772-guix-latest/guix/scripts/import/hackage.scm"]
>> In ice-9/eval.scm:
>> 453: 1 Exception thrown while printing backtrace:
>> ERROR: In procedure package-location: Wrong type argument: Error while printing exception.
>>
>> ice-9/eval.scm:387:11: In procedure eval:
>> ice-9/eval.scm:387:11: In procedure package-version: Wrong type argument: Error while printing exception.
>> builder for `/gnu/store/pc1i5s6vx9yx97prhskx178gj5swxw4k-guix-latest.drv' failed with exit code 1
>> guix pull: error: build failed: build of `/gnu/store/pc1i5s6vx9yx97prhskx178gj5swxw4k-guix-latest.drv' failed
>>
>> Any idea?
>>
>> To me it sounds like there are two <package> record type descriptors in
>> the wild, which is why ‘package-location’ in the package record printer
>> bails out.
>
> That's one of the errors that result from a "bad" order of compiling the
> files and when the 'load' hack isn't used to work around it, which isn't
> the case in that patch... Indeed I can't seem to reproduce the issue.
>
> The attached patch below also builds on the quoted patch, removes the
> thread-safe-port procedure, and just sets the warning port to a void
> port. Applied on top of the current master, it works for me.
On top of current master, it fails for me in the same way as above.
To be clear, I applied the patch, ran ‘make dist’, and then:
time ./pre-inst-env guix pull --url=file://$PWD/guix-0.9.0.tar.gz
Are you doing the same? The “loading” part is done sequentially, so it
should be deterministic.
> Thanks for picking this up and sorry that I couldn't finish it. :-)
No problem, we’re getting there! :-)
Ludo’.
next prev parent reply other threads:[~2015-11-27 10:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 17:10 [PATCH] build: pull: Compile .scm files in one process Taylan Ulrich Bayırlı/Kammer
2015-11-05 21:06 ` Ludovic Courtès
2015-11-06 8:56 ` Taylan Ulrich Bayırlı/Kammer
2015-11-06 20:50 ` Ludovic Courtès
2015-11-07 9:54 ` Taylan Ulrich Bayırlı/Kammer
2015-11-10 18:00 ` Ludovic Courtès
2015-11-11 12:12 ` Taylan Ulrich Bayırlı/Kammer
2015-11-11 13:26 ` Ludovic Courtès
2015-11-12 10:23 ` Taylan Ulrich Bayırlı/Kammer
2015-11-12 12:07 ` Andy Wingo
2015-11-12 12:27 ` Taylan Ulrich Bayırlı/Kammer
2015-11-12 12:36 ` Andy Wingo
2015-11-12 13:52 ` Taylan Ulrich Bayırlı/Kammer
2015-11-12 20:44 ` Ludovic Courtès
2015-11-13 14:28 ` Taylan Ulrich Bayırlı/Kammer
2015-11-14 14:54 ` Ludovic Courtès
2015-11-26 22:20 ` Ludovic Courtès
2015-11-27 8:53 ` Taylan Ulrich Bayırlı/Kammer
2015-11-27 10:07 ` Ludovic Courtès [this message]
2015-11-27 15:16 ` Taylan Ulrich Bayırlı/Kammer
2015-11-30 13:04 ` Ludovic Courtès
2015-12-02 8:09 ` Taylan Ulrich Bayırlı/Kammer
2015-12-03 10:44 ` Ludovic Courtès
2015-12-21 9:49 ` Taylan Ulrich Bayırlı/Kammer
2016-01-05 17:56 ` Taylan Ulrich Bayırlı/Kammer
2016-01-05 21:39 ` Ludovic Courtès
2016-01-05 22:32 ` Taylan Ulrich Bayırlı/Kammer
2016-01-07 17:01 ` Leo Famulari
2016-01-07 17:54 ` Alex Sassmannshausen
2016-01-07 18:10 ` Ludovic Courtès
2015-12-03 15:27 ` Mark H Weaver
2015-12-03 15:54 ` Taylan Ulrich Bayırlı/Kammer
2015-12-04 14:11 ` Ludovic Courtès
2015-11-06 16:12 ` Andy Wingo
2015-11-06 16:41 ` Taylan Ulrich Bayırlı/Kammer
2015-11-06 20:48 ` Ludovic Courtès
2015-11-09 7:41 ` Andy Wingo
2015-11-09 8:51 ` Taylan Ulrich Bayırlı/Kammer
2015-11-09 9:07 ` Andy Wingo
2015-11-09 9:50 ` Taylan Ulrich Bayırlı/Kammer
2015-11-09 10:49 ` Andy Wingo
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=87bnafbvrs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).