Hello,
I encountered this issue today. This looks like a pretty complete
solution ready to go. Did this ever make it into Guile/Guix?
(Ironically I was also reaching for a "make-custom-textual-output-port"
the other day!)
--
Sarah
Mark H Weaver writes:
> Hi Ludovic,
>
> Ludovic Courtès
Hi Ludovic,
Ludovic Courtès writes:
> Mark H Weaver skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> So there are two things. To fix the issue you reported (build output
>>> that goes through), I think we must simply turn off UTF-8 decoding from
>>> ‘process-stderr’ and leave that
Hi Mark,
Mark H Weaver skribis:
> Ludovic Courtès writes:
[...]
>> So there are two things. To fix the issue you reported (build output
>> that goes through), I think we must simply turn off UTF-8 decoding from
>> ‘process-stderr’ and leave that entirely to ‘build-event-output-port’.
>
>
Hi Ludovic,
Ludovic Courtès writes:
> Mark H Weaver skribis:
>
>> Ludovic Courtès writes:
>>
>>> The third read(2) call here ends on a partial UTF-8 sequence for LEFT
>>> SINGLE QUOTATION MARK (we get the first two bytes of a three byte
>>> sequence.)
>>>
>>> What happens is that
Hi Mark,
Mark H Weaver skribis:
> Ludovic Courtès writes:
>
>> The third read(2) call here ends on a partial UTF-8 sequence for LEFT
>> SINGLE QUOTATION MARK (we get the first two bytes of a three byte
>> sequence.)
>>
>> What happens is that ‘process-stderr’ in (guix store) gets that byte
>>
Here's version 3 with much more precise specifications in the
docstrings. If I recall correctly, the code itself is identical to
version 2.
Mark
;;; Copyright © 2019 Mark H Weaver
;;;
;;; This program is free software: you can redistribute it and/or modify
;;; it under the terms of the
Here's an improved version of the code with doc strings. It also
properly handles the case of (target-source >= target-end) in
'utf8->string!'.
Mark
;;; Copyright © 2019 Mark H Weaver
;;;
;;; This program is free software: you can redistribute it and/or modify
;;; it under the terms of
Hi Ludovic,
Thanks for investigating this.
Ludovic Courtès writes:
> The third read(2) call here ends on a partial UTF-8 sequence for LEFT
> SINGLE QUOTATION MARK (we get the first two bytes of a three byte
> sequence.)
>
> What happens is that ‘process-stderr’ in (guix store) gets that byte
>
Hi Mark,
Mark H Weaver skribis:
> Ludovic Courtès writes:
>
>> Mark H Weaver skribis:
>>
>>> Sometimes when compiling a package with --verbosity=1, some parts of the
>>> compile output leak through. For example, see the transcript below.
>>
>> Weird.
>
> FWIW, a few observations, possibly
> What’s the value of --max-jobs?
max-jobs is 1. Please disregard my previous response.
Thanks,
Mark
Sometimes when compiling a package with --verbosity=1, some parts of the
compile output leak through. For example, see the transcript below.
Mark
--8<---cut here---start->8---
mhw@jojen ~$ guix system build /etc/config.scm --verbosity=1 --keep-failed
11 matches
Mail list logo
