Vivien Kraus <[email protected]> writes: > The string failure is due to a dotted circle as a basis for the > combining character, that may have been inserted by a clever source code > editor. Replacing it with the hex value for the character itself, the > test passes.
Sorry, the phase name is not good, because it’s not a problem with the guile reader but a problem with the source code. So, this should be better. Vivien
>From ce832d8593413f4a812211f2fbd98ab5086fe2a2 Mon Sep 17 00:00:00 2001 From: Vivien Kraus <[email protected]> Date: Tue, 2 Nov 2021 18:19:03 +0100 Subject: [PATCH] guile-gi: fix a source code encoding error * gnu/packages/guile-xyz.scm (guile-gi) [phases]: remove the default dotted circle from the combining character that is tested in test/string.scm. --- gnu/packages/guile-xyz.scm | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/gnu/packages/guile-xyz.scm b/gnu/packages/guile-xyz.scm index 3c93779209..8fc37d2069 100644 --- a/gnu/packages/guile-xyz.scm +++ b/gnu/packages/guile-xyz.scm @@ -3145,6 +3145,10 @@ (define-public guile-gi (ice-9 rdelim)) #:phases (modify-phases %standard-phases + (add-after 'unpack 'remove-dotted-circle-from-combining-character + (lambda* _ + (substitute* "test/string.scm" + (("#\\\\◌̀") "#\\x0300")))) (add-after 'unpack 'patch-references-to-extension (lambda* (#:key outputs #:allow-other-keys) (let ((effective (read-line -- 2.33.1
