From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ghc: allow building with current Sphinx
Date: Tue, 20 Jul 2021 22:07:24 +0200 [thread overview]
Message-ID: <20210720200724.5g2TjqUibzkEaibLwhpTETmaTk05_UoiqVipF_kxkT0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31898@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
There's a merged pull request on the void-packages repository
ghc: allow building with current Sphinx
https://github.com/void-linux/void-packages/pull/31898
Description:
./srcpkg build ghc fails with current tools:
"inplace/bin/ghc-stage1" [...] /build/cbits/longlong.p_o
Running Sphinx v4.0.2
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)
...
make: *** [Makefile:128: all] Error 2
According to https://gitlab.haskell.org/ghc/ghc/-/issues/19962
>> This fix is to use raw strings, as already done in master:
>> https://gitlab.haskell.org/ghc/ghc/-/blob/master/docs/users_guide/conf.py#L96
Sanitized from commit (only small parts apply)
https://gitlab.haskell.org/ghc/ghc/-/commit/83407ffc7acc00cc025b9f6ed063add9ab9f9bcc
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
[skip CI] build might take over 3 hours with a single CPU - local build/pkg tested
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
prev parent reply other threads:[~2021-07-20 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 21:17 [PR PATCH] " chexum
2021-07-11 12:08 ` chexum
2021-07-17 3:36 ` [PR REVIEW] " ericonr
2021-07-17 7:44 ` chexum
2021-07-18 21:11 ` ericonr
2021-07-18 21:19 ` [PR PATCH] [Updated] " chexum
2021-07-20 20:07 ` ericonr
2021-07-20 20:07 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210720200724.5g2TjqUibzkEaibLwhpTETmaTk05_UoiqVipF_kxkT0@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).