[pdftex] pdflatex failures on big-endian architectures (s390x / ppc64)

[Ross Moore]

Hi again.

On 24 Oct 2023, at 12:56 pm, Ross Moore <ross.moore at mq.edu.au> wrote:

Hi Hilmar, Karl, Thanh

Generating the  ToUnicode  resources is failing.

Here are some simple first tests that may be worth doing.

1. Check the availability of some files:


rossmoore at ITS-C02GC05JQ05P uncompressed % kpsewhich glyphtounicode.tex glyphtounicode-cmr.tex

/usr/local/texlive/2023/texmf-dist/tex/generic/pdftex/glyphtounicode.tex

/usr/local/texlive/2023/texmf-dist/tex/latex/pdfx/glyphtounicode-cmr.tex


2. Add the line to your LaTeX preamble:

    \input glyphtounicode.tex

That should give you the correct  /ToUnicode  resource for the commonest fonts.
If not, then the compiled pdfTeX figures to be wrong.

If so, then the question becomes, why wasn’t  glyphtounicode.tex
automatically compiled-in, when  pdfTeX was created for the PPC 2023 version ?
Or when the LaTeX format file was generated for it?
In any case you then have a relatively easy workaround.


BTW, I’m using  arm64  and have no such issue, under TeXLive 2023.


Hope this helps.

    Ross



Have a look at the attached file, generated with:

rossmoore at ITS-C02GC05JQ05P uncompressed % ls *.pdf
1054218_amd64_uncomp.pdf 1054218_ppc64_uncomp.pdf
rossmoore at ITS-C02GC05JQ05P uncompressed % diff -a *.pdf > diffs.txt


With

> /PTEX.Fullbanner (This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) kpathsea version 6.3.5)

the ToUnicode map is all  <0000>s  .

But it’s OK with

< /PTEX.Fullbanner (This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) kpathsea version 6.3.4)


Hope this helps you track the cause.


Cheers.

Ross



Hilmar
--
Testmail

<1054218_amd64_uncomp.pdf><1054218_amd64_uncomp.tex><1054218_ppc64_uncomp.pdf><1054218_ppc64_uncomp.tex>

<diffs.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/pdftex/attachments/20231024/610992af/attachment-0001.htm>