<mark_weaver>one issue is that the guix builder can't install setuid binaries. I don't know what the plan is for that.
<davexunit>sudo's configure script checks for the presence of programs like mv, bash, vi, and sendmail. it has hardcoded a set of possible paths. in the case of mv, the paths it checks are "/usr/bin/mv" "/bin/mv" "/usr/ucb/mv" "/usr/sbin/mv"
<davexunit>when mv is found, _PATH_MV is defined. mv is not found when I build when I include coreutils as an input.
<davexunit>and the build fails because of the undefined _PATH_MV
<davexunit>should one of those paths work at all when building? do I need to patch the configure script somehow?
<mark_weaver>typically that's solved by adding a phase that uses 'substitute*' to replace those paths with the corresponding exact paths.
<mark_weaver>davexunit: normally, if you have to remove a flag that would be added automatically, it indicates that it's a custom configure script, and you probably need to replace the configure phase with a new one.
<phant0mas>okay, till I figure out what's wrong I will just redirect the output to a file
<mark_weaver>phant0mas: I should mention another possibility: if you look at the log for a build that's currently in progress, there will usually output that has not yet been written to the file, because it's compressed with bz2 which is a block compressor.
<Steap>civodul: should I do the Python patch for core-updates or for master ?
<davexunit>where do I look for my failed builds? /gnu/store? I started guix-daemon with the --cache-failures flag but I can't find the cache.
<davexunit>I find a .drv file corresponding to the failed build, but I'm looking for a directory where I can find the generated log files.
<civodul>Steap: core-updates is no more, so for master :-)
<civodul>davexunit: --cache-failures just means that it won't attempt to rebuild something known to fail
<civodul>those failures are stored in the sqlite db
<davexunit>civodul: oh okay, I misread then. there's a test suite log file that I need to see to debug my package recipe.
<mark_weaver>davexunit: build it with "guix build -K <foo>" and then it will be left in /tmp/nix-build-*
<davexunit>I should've looked at the guix build switches. I just assumed it was something that the daemon controlled. thanks.
<mark_weaver>civodul: speaking of cached failures, I get the impression that hydra.gnu.org is caching failures that were transient network problems, or something. for whatever reason, there are hundreds of packages not being built, despite the fact that I attempted a build of the newest version of every package we have on my x86_64, and only a small number failed.
<Steap>civodul: oh, we never do two merges of core-updates ?