Andreas Enge andr...@enge.fr skribis:
Am Samstag, 23. Februar 2013 schrieb Ludovic Courtès:
(make-regexp
^[[:blank:]]*([[:graph:]]+)[[:blank:]]*([[:graph:]]*)(.*)$)))
I think it should be a + after the second [[:blank:]], because there
should be space between the interpreter name and its
Am Freitag, 22. Februar 2013 schrieb Andreas Enge:
Please find attached a patch for review. I tested it on a few example
files, but not yet with a real packet - I am waiting for the full
rebuild ;-)
I had test failures in coreutils, and to check whether it was related to my
patch, I tried
Andreas Enge andr...@enge.fr skribis:
I had test failures in coreutils,
Do you still have the details around? ‘env’ is part of Coreutils, so it
may be that it’s testing its behavior, and that patching prevents that.
Perhaps ‘patch-shebang’ could have a ‘patch-env?’ keyword parameter,
Am Samstag, 23. Februar 2013 schrieb Ludovic Courtès:
Andreas Enge andr...@enge.fr skribis:
I had test failures in coreutils,
Do you still have the details around? ‘env’ is part of Coreutils, so it
may be that it’s testing its behavior, and that patching prevents that.
This was also my
Andreas Enge andr...@enge.fr skribis:
For info about why this happens, you could try:
guile -c '(pk (@ (guix ui) guix-main))'
[...]
In unknown file:
?: 0 [memoize-variable-access! #memoized (@ (guix ui) guix-main) #f]
ERROR: In procedure memoize-variable-access!:
ERROR: In procedure
Am Donnerstag, 21. Februar 2013 schrieb Nikita Karetnikov:
What should I try now?
Did you already get the glibc, or did the problems appear before? Maybe it
would be enough to just replace the glibc with one that contains the 64 bit
headers.
I tried to compile glibc independently with
