Re: Failed: phase compiling: caca-0.99.beta19-5 failed

Debian is still at 0.9.beta19 and they have a different patch to that makefile recipe:

https://sources.debian.org/patches/libcaca/0.99.beta19-2.2/100_doxygen.diff

dan

On 2/16/22, 7:30 AM, "Hanspeter Niederstrasser" <[email protected]> wrote:

    On 2/15/22 3:45 PM, Justin Hallett wrote:
    > Sorry,
    > 
    > It’s not fs, it’s the new texlive, the pdf creation is failing, this isn’t a bug in caca it’s in texlive.
    > 
    > I can’t even install the new texlive so I can’t even test this.
    > 
    > - Justin
    > 
    >> On Feb 15, 2022, at 2:24 PM, Franchetti, Giuliano Dr. <[email protected]> wrote:
    >>
    >> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2021/Fink 20210325-6) (preloaded format=pdflatex)
    >> restricted \write18 enabled.
    >> entering extended mode
    >> (./refman.tex
    >> LaTeX2e <2020-10-01> patch level 4
    >> L3 programming layer <2021-02-18>
    >> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2021/Fink 20210325-6) (preloaded format=pdflatex)
    >> restricted \write18 enabled.
    >> entering extended mode
    >> (./refman.tex
    >> LaTeX2e <2020-10-01> patch level 4
    >> L3 programming layer <2021-02-18>
    >> pdflatex exit code: 1
    >> mv latex/refman.pdf latex/libcaca.pdf
    >> mv: rename latex/refman.pdf to latex/libcaca.pdf: No such file or directory
    >> make[2]: *** [stamp-latex] Error 1
    >> make[1]: *** [all-recursive] Error 1

    Looks like caca 0.99beta19 is ancient (from 2013) and that breaks with 
    the texlive2021. Upstream actually released a new version beta20 in 
    October 2021 (almost as good a release cycle as us) that claims to fix a 
    latex documentation hack from 2004:

    [1] https://github.com/cacalabs/libcaca/tags
    [2] 
    https://github.com/cacalabs/libcaca/commit/b7d7a7a35c7d0f737494c04bc68e51358a784de7

    I tried it and it actually starts building the PDF, but the pdfTeX 
    output has lots of errors about missing marks

    > l.64 \end{longtabu}
    >                    
    > I can't figure out why you would want to use a tab mark
    > or \cr or \span just now. If something like a right brace
    > up above has ended a previous alignment prematurely,
    > you're probably due for more error messages, and you
    > might try typing `S' now just to see what is salvageable.


    Hanspeter


    _______________________________________________
    Fink-users mailing list
    [email protected]
    List archive:
    https://sourceforge.net/p/fink/mailman/fink-users/
    Subscription management:
    https://lists.sourceforge.net/lists/listinfo/fink-users





_______________________________________________
Fink-users mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users