waf and Python 3.7

[Joel Sherrill]

On Tue, Dec 18, 2018 at 5:33 PM Chris Johns <chrisj at rtems.org> wrote:

> On 19/12/2018 06:12, Christian Mauderer wrote:
> > I updated waf in rtems-tools with a reference to the ticket. I'm still a
> > little unsure about our tickets: Should I create separate tickets for
> > that problem in rtems-docs, rtems-libbsd (both have the same problem)
> > and examples-v2 (I haven't tested that yet but I would expect the
> > problem there too).
>
> No, the same ticket should be fine. Maybe update the ticket's details to
> highlight this is happening. Separate tickets are needed for separate
> branches
> because the timeline cannot be shared.
>
> > Note that rtems-docs needs an extra patch to build with python 3. There
> > is an indentation error (mix of space and tab).
>
> Yes I have tripped over this but I have not had time to push a fix.
> Building PDF
> is broken for me with the latest Sphinx. I am on a fully updated FreeBSD
> 11.2-p5
> and all packages are updated plus the latest Sphinx in a virtualend. The
> issue
> seems to be deep in Latex and relates to unicode characters in bib entries
> with
> hyperef and the other package and things being confused. I do not know if
> it is
> a bug in Sphinx or our configuration.
>

FWIW I am building html fine with Python 2 and Sphinx 1.6, 1.7, and 1.8.2
on three
different CentOS computers. But PDF doesn't work on any of those platforms.

>
> > Beneath that I receive a
> > "master file /home/christian/archive/rtems-docs/user/contents.rst not
> > found" error even with a clean checkout which seems a little odd. I'll
> > create patches as soon as I found out why it doesn't work as intended.
>
> I am sorry I am not sure, I would need to look and see.
>

I'm not seeing this on any of those. Maybe Python 3. I can build cleanly
as long as I stick to HTML.

--joel

>
> Thanks
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181218/6b22f178/attachment-0002.html>