Bug#995429: ghc ftbfs in unstable (after fixing the autoconf issue)
Ilias Tsitsimpis
iliastsi at debian.org
Sun Oct 3 12:10:17 BST 2021
Hi Matthias,
On Fri, Oct 01, 2021 at 09:05AM, Matthias Klose wrote:
> after fixing the autoconf 2.7x issue, the ghc build still fails with:
>
> [...]
> rts/RetainerSet.c: In function ‘printRetainerSetShort’:
>
> rts/RetainerSet.c:241:21: error:
> warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 241 | tmp[max_length] = '\0';
> | ~~~~~~~~~~~~~~~~^~~~~~
> |
> 241 | tmp[max_length] = '\0';
> | ^
>
> rts/RetainerSet.c:235:10: error:
> note: at offset [-9223372036854775808, 9223372036854775807] to an object
> with size at most 4294967295 declared here
> 235 | char tmp[max_length + 1];
> | ^~~
> |
> 235 | char tmp[max_length + 1];
> | ^
I believe the above messages are not the reason why the build failed,
since these are warnings. When I tried building (after fixing the
autoconf 2.7x issue) it failed with:
Running Sphinx v4.2.0
Configuration error:
There is a syntax error in your configuration file: (unicode error) 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX escape (conf.py, line 87)
GHC fails to build with the newer version of Sphinx available in
unstable. After fixing the Sphinx issue, I succeeded on building GHC on
unstable again. I will upload a new version now fixing these issues.
Thanks,
--
Ilias
More information about the Pkg-haskell-maintainers
mailing list