Re: Building All Output Formats for RTEMS Docs

2016-11-08 Thread Chris Johns
On 8/11/16 9:32 am, Christian Mauderer wrote: > > it would be nice if there are some good visible warnings if fallback packages > are used. Otherwise it might be hard for someone building the documentation > to find out why the output looks different. > At the moment there is a configure warni

Re: Building All Output Formats for RTEMS Docs

2016-11-07 Thread Christian Mauderer
- Ursprüngliche Mail - > Von: "Chris Johns" > An: "Christian Mauderer" > CC: "RTEMS Devel" > Gesendet: Montag, 7. November 2016 23:23:42 > Betreff: Re: Building All Output Formats for RTEMS Docs > On 07/11/2016 19:27, Christian Maudere

Re: Building All Output Formats for RTEMS Docs

2016-11-07 Thread Chris Johns
On 07/11/2016 19:27, Christian Mauderer wrote: with your patch that removes lato and inconsolata, there are now fewer packages necessary on Arch. It is now not longer necessary to install the quite large texlive-fontsextra (nearly 700MB). Beneath that, the pygmentize packet has somehow been l

Re: Building All Output Formats for RTEMS Docs

2016-11-07 Thread Joel Sherrill
For CentOS, I am trying to install the Texlive version now. It is taking a LONG time. It had an estimated install time of about 4 hours and died on the first attempt. If this works on CentOS 6, then I will repeat for CentOS 7 and Fedora 23. If all goes well, this can be the recommended solution on

Re: Building All Output Formats for RTEMS Docs

2016-11-07 Thread Christian Mauderer
> On 07/11/2016 09:40, Christian Mauderer wrote: >> >> I tested to build the documentation on Arch Linux. I had to install some >> additional packages (see attached patch 2) and I had to work around a >> TypeError >> (see first part of attached error.log and patch 1) during the "waf >> configure"

Re: Building All Output Formats for RTEMS Docs

2016-11-06 Thread Chris Johns
On 07/11/2016 09:40, Christian Mauderer wrote: I tested to build the documentation on Arch Linux. I had to install some additional packages (see attached patch 2) and I had to work around a TypeError (see first part of attached error.log and patch 1) during the "waf configure". Sorry about

Re: Building All Output Formats for RTEMS Docs

2016-11-06 Thread Christian Mauderer
Hello Chris, I tested to build the documentation on Arch Linux. I had to install some additional packages (see attached patch 2) and I had to work around a TypeError (see first part of attached error.log and patch 1) during the "waf configure". While building there was another tool missing (pyg

Re: Building All Output Formats for RTEMS Docs

2016-11-05 Thread Chris Johns
On 5/11/16 1:27 am, Joel Sherrill wrote: > On Fri, Nov 4, 2016 at 1:35 AM, Sebastian Huber > > wrote: > > Hello Chris, > > works fine on openSUSE 13.1. I installed a couple of texinfo > packages: Ouch that is not great. Needing that package

Re: Building All Output Formats for RTEMS Docs

2016-11-04 Thread Joel Sherrill
On Fri, Nov 4, 2016 at 1:35 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Chris, > > works fine on openSUSE 13.1. I installed a couple of texinfo packages and > did a "pip install -U Sphinx". > > Chris was trying on one of our CentOS 7 machines. I tried on a Fedora 23 ma

Re: Building All Output Formats for RTEMS Docs

2016-11-03 Thread Sebastian Huber
Hello Chris, works fine on openSUSE 13.1. I installed a couple of texinfo packages and did a "pip install -U Sphinx". -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu.

Building All Output Formats for RTEMS Docs

2016-11-03 Thread Chris Johns
Hi, Help needed so please read. Building the RTEMS Documentation for HTML is easy. You need to install Sphnix and it should run. There is a README.txt in the top directory of rtems-docs.git repo and I have add FreeBSD and a little bit for CentOS 7. I would welcome patches to the README.txt fo