Hi Dmitry,
On Sun, 23 Feb 2020 23:52:25 +0300, Дмитрий Дьяченко wrote:
> Hello, Paul,
>
> I check FAQ-BUILD.txt and find Q. 10.A
> " ... and TeX Live releases prior to 2020 (epigraph)".
>
> I update livetex today and probably I have the latest epigraph' version
> ./texlive/texmf-dist/tex/latex/epigraph:
> total 8
> -rw-r--r--. 1 dima dima 4602 Jan 3 01:06 epigraph.sty
So, you are using upstream TeX Live 2019, not the one distributed by
Fedora.
Due to the fairly massive updates in LaTeX base package to be released
in TeX Live 2020, current upstream TeX Live lost compatibility with
the "examplep" package.
I contacted the author of the package about this issue, but have not
heard from him yet.
As a matter of fact, I have a patch set to resolve the issue in case
the breakage persists. My thought was to submit it if Ubuntu/Fedora
picks up the broken state of TeX Live in the next release.
Now that you have encountered the issue, I'm submitting it for you
to test.
Thanks, Akira
>
> To avoid make clean/make problems I
> -- rm build-perfbook
> -- update perfbook
> -- copy perfbook into build-perfbook
> -- run make in clean dir.
>
> I use Fedora 31 up-to-day, x86_64.
>
> I 'll try tomorrow to find the first commit after 07 feb with errors.
>
> Thank you,
> Dmitry
>
> вс, 23 февр. 2020 г. в 21:47, Paul E. McKenney <paulmck@xxxxxxxxxx>:
>>
>> On Sun, Feb 23, 2020 at 07:49:32PM +0300, Дмитрий Дьяченко wrote:
>>> Hello!
>>>
>>> I build perfbook sometimes and try build today after read 'Toward second
>>> edition' letter.
>>> I use up-to-day livetex and up-to-day perfbook.
>>>
>>> 07-feb-2020 build PASS.
>>> Today build FAIL [1].
>>
>> Hello, Dmitry,
>>
>> There was a change in the build system to fix a rendering problem.
>> Could you please check recent changes to FAQ-BUILD.txt and see if they
>> apply to you? It might be necessary for you download epigraph.zip,
>> depending on what distro version you happen to be using. (I had to
>> download it, for example.)
>>
>> Either way, does "make clean" followed by "make" help?
>>
>> Thanx, Paul
>>
>>> Thank you,
>>> Dmitry
>>>
>>> [1] make
>>> [...]
>>> echo > origpub.tex
>>> latexpand --empty-comments perfbook.tex 1> perfbook_flat.tex 2> /dev/null
>>> sh utilities/extractqqz.sh < perfbook_flat.tex | perl utilities/
>>> qqzreorder.pl > qqz.tex
>>> cat perfbook_flat.tex qqz.tex | sh utilities/extractcontrib.sh > contrib.tex
>>> sh utilities/extractorigpub.sh < perfbook_flat.tex > origpub.tex
>>> sh utilities/runfirstlatex.sh perfbook
>>> pdflatex 1 for perfbook.pdf
>>>
>>> LaTeX Warning: Reference `ln:toolsoftrade:Inviting a Store-to-Load
>>> Conversion:l
>>> oad:p' on page 42 undefined on input line 1988.
>>>
>>>
>>> ! Package examplep Error: \PVerb inner delimiter must be brace,
>>> (examplep) not backslash or control sequence or active char.
>>>
>>> See the examplep package documentation for explanation.
>>> Type H <return> for immediate help.
>>> ...
>>>
>>> l.1988 ...load:p} fetches \co{p}, but the \qco{if}
>>> statement on
>>> ?
>>> ! Emergency stop.
>>> ...
>>>
>>> l.1988 ...load:p} fetches \co{p}, but the \qco{if}
>>> statement on
>>> Try typing <return> to proceed.
>>> ----- Fatal latex error, see perfbook.log for details. -----
>>> make: *** [Makefile:183: perfbook.aux] Ошибка 1
>>> Command exited with non-zero status 2
>>>
>>> вс, 23 февр. 2020 г. в 18:33, Paul E. McKenney <paulmck@xxxxxxxxxx>:
>>>
>>>> Hello!
>>>>
>>>> I finally found and fixed the rcu_barrier() bug [1], so I should again
>>>> be able to devote some big-system test time to redoing performance
>>>> results in perfbook. Once that is done, I expect that it is time for
>>>> the second edition.
>>>>
>>>> I might also convert the blank page hiding the solution to the Dining
>>>> Philosophers Problem to a quick quiz, but I consider this optional.
>>>>
>>>> Are there any other changes that are needed? [2]
>>>>
>>>> Thanx, Paul
>>>>
>>>>
>>>> [1] The fix is at 77abca1c358a ("rcu: Make rcu_barrier() account for
>>>> offline no-CBs CPUs") in -rcu, in case anyone is curious.
>>>>
>>>> [2] Here is a list of some things that I believe can follow the second
>>>> edition:
>>>>
>>>> Expand lock-free algorithm discussion to include LIFO push,
>>>> illustrating the infamous pointer-zap issue. (See ISO SC22
>>>> WG21 P1726R3, which should appear in a couple of weeks, for
>>>> more details.)
>>>>
>>>> Add text describing the Issaquah Challenge.
>>>>
>>>> Add text describing skiplists, one of the more concurrency
>>>> friendly data structures.
>>>>
>>>> Add text describing data-race detectors such as KCSAN. (This needs
>>>> to wait for more Linux-kernel experience.)
>>>>
>>>> Additional material from todo.txt. ;-)
>>>>
