On 03/03/2020 17:15, Marius Bakke wrote:
Pádraig Brady <[email protected]> writes:It builds fine, and reproducibly on Guix System (current master; ba8992d28b1616d05b7cb04ef032944c5d19cd5a); build log attached. Guix has been disabling tests/misc/env-S.pl ;; This test hits the 127 character shebang limit in the build ;; environment due to the way "env -S" splits arguments into ;; shebangs. Note that "env-S-script.sh" works around this ;; specific issue, but "env-S.pl" is not adjusted for build ;; environments with long prefixes (/tmp/guix-build-...). (substitute* "Makefile" (("^.*tests/misc/env-S.pl.*$") ""))I don't immediately see the issue with env-S.pl TBHThe problem with tests/misc/env-S.pl is that it needs "env" pre-installed and residing in either /bin or /usr/bin, which do not exist in the Guix build container. From running it through 'strace': 430 write(2, "split -S: 'A=B \\\\c'\n", 21) = 21 430 write(2, " into: 'A=B'\n", 16) = 16 430 write(2, "cleaning environ\n", 17) = 17 430 write(2, "setenv: A=B\n", 14) = 14 430 write(2, "executing: env\n", 15) = 15 430 write(2, " arg[0]= 'env'\n", 17) = 17 430 execve("/bin/env", ["env"], 0x22ce580 /* 1 var */) = -1 ENOENT (No such file or directory) 430 execve("/usr/bin/env", ["env"], 0x22ce580 /* 1 var */) = -1 ENOENT (No such file or directory) 430 write(2, "env: ", 5) = 5 430 write(2, "'env'", 5) = 5 430 write(2, ": No such file or directory", 27) = 27 430 write(2, "\n", 1) = 1 430 close(1) = 0 430 close(2) = 0 430 exit_group(127) = ? 430 +++ exited with 127 +++ I can't figure out where /bin and /usr/bin comes from. 'env' is available on PATH during the build, but that does not suffice here.
I don't see /bin/env being used here. Perhaps PATH is being adjusted in your environment. It's a good clue anyway, so thanks for the info. I don't think this warrants holding up the release though. cheers, Pádraig
