On Fri, Aug 12, 2022 at 1:06 AM Chris Johns <chr...@rtems.org> wrote:
> On 12/8/2022 6:10 am, Joel Sherrill wrote: > > > > Subject says it. This is the error and a git bisect which points to Chris > > updating the arm section of the user guide. I don't see the issue > looking at the > > patch. > > > > From f028448e5f21f4317a0a7b9b336d7e492ebea6c7 Mon Sep 17 00:00:00 2001 > > From: Chris Johns <chr...@rtems.org <mailto:chr...@rtems.org>> > > Date: Wed, 3 Aug 2022 14:20:52 +1000 > > Subject: [PATCH rtems-docs] versions: Update arm > > > > Error output followed by git bisect. > > > > Build: 6.f028448 (3rd August 2022) > > [4/7] Compiling build/user/latex/user.tex > > first pass on pdflatex > > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019) (preloaded > > format=pdflatex) > > \write18 enabled. > > entering extended mode > > The issue is the change I made to the ARM BSP to correctly handle section > numbering and TOC. This changed the depth the source builds from and that > has > changed the relative path to the BBB P2 debug connector image. HTML does > not > generate an error however PDF does. I will push the fix. > Thank you. I can confirm this works. I know it takes longer but every time I build docs, I build pdf and html. It is odd cases like this that point out why it is good to let it build and come back to check on it. > > I will also push a change to the pdflatex build that sets the TEXINPUTS env > variable to include some sphinx latex support that was being silently > ignored. > Great! Will this have any visible change on output? --joel > > Chris >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
