[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libtomcrypt FTBFS: Undefined control sequence \writestatus



Thanks for looking into this! I sent your suggested changes upstream at https://github.com/libtom/libtomcrypt/pull/255, which will hopefully be included in the upcoming v1.18.0 release, which is just around the corner.

On Tue, Aug 1, 2017 at 7:52 AM, Norbert Preining <norbert@preining.info> wrote:
Hi

there are two errors here, one is bad, but harmless:


> (preloaded format=pdflatex)
                    ^^^^^^^^

> *geometry* detected driver: dvips
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

because there is a line
        \usepackage[dvips]{geometry}

Please don't specify dvips when you use pdflatex.


Now for the "bug" is that
        \undefined
is used in many places to check for whether a macro is undefined.
By including the
        \def\undefined...
in crypt.tex this breaks tests in suppp-pdf.mkii and probably some
other places, too.

I guess it was just by luck that it worked previously, newer TL
loads various epstopdf support to transparently allow for inclusion
of all kind of images.

The trivial fix is simply to *remove* the definition of \undefined
since it is *NEVER* used in the document.

Best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc.     +    JAIST     +    TeX Live     +    Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



--
Best regards,
Michael

Reply to: