[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging cycles in build
From: |
Ludovic Courtès |
Subject: |
Re: debugging cycles in build |
Date: |
Wed, 26 Jul 2017 23:11:21 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Dave Love <address@hidden> skribis:
> I changed a package to have a "lib" output, which failed because it
> detected a cycle (whereas it's OK with everything in "out"). Is there a
> good way to debug that?
No good way unfortunately. I usually build with -K and then do
something like:
LC_ALL=C grep -r OUTPUT2 OUTPUT1
which kinda works, except if the reference comes from a symlink, in
which case you can do something like:
tar cf O2.tar OUTPUT2
grep OUTPUT1 O2.tar
and/or open O2.tar in Emacs with hexl-mode.
This is inconvenient but doable.
> I couldn't easily find the code implementing the check.
The check is done by guix-daemon, whose C++ code base is under nix/.
HTH!
Ludo’.