Bug 250680 - devel/avr-libc DOXYGEN knob fails build
Summary: devel/avr-libc DOXYGEN knob fails build
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Joerg Wunsch
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-28 02:59 UTC by alt2600
Modified: 2020-11-02 22:09 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (joerg)


Attachments
refman.out (219.58 KB, text/plain)
2020-10-29 02:21 UTC, alt2600
no flags Details
build log, truncated for just document build (60.97 KB, text/plain)
2020-10-29 02:31 UTC, alt2600
no flags Details
latex_src ls output (2.98 KB, text/plain)
2020-10-29 20:15 UTC, alt2600
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description alt2600 2020-10-28 02:59:58 UTC
port builds fine without the DOXYGEN knob set, but with it it fails as indicated below. This all appears to be during the documentation generation stage. I have replaced transfig with fig2dev as it seems the dependancy was changed. It fails with transfig and fig2dev, I only have fig2dev installed now.



This is pdfTeX, Version 3.14159265-2.6-1.40.16 (Web2C 2015) (preloaded format=pdflatex)
 restricted \write18 enabled.
Fixing transparency for malloc-x1.png
entering extended mode
(./refman.tex
LaTeX2e <2015/01/01> patch level 2
Babel <3.9l> and hyphenation patterns for 79 languages loaded.

Fixing transparency for malloc-x2.png
Fixing transparency for nav_f.png
Fixing transparency for nav_g.png
Fixing transparency for nav_h.png
Fixing transparency for open.png
Fixing transparency for releases.png
Fixing transparency for splitbar.png
Fixing transparency for sync_off.png
Fixing transparency for sync_on.png
Fixing transparency for tab_a.png
Fixing transparency for tab_b.png
Fixing transparency for tab_h.png
Fixing transparency for tab_s.png
echo timestamp > fix_png
gmake[5]: *** [Makefile:8: refman.pdf] Error 1
gmake[5]: Leaving directory '/usr/ports/devel/avr-libc/work/avr-libc-2.0.0/doc/api/latex_src'
gmake[4]: *** [Makefile:639: avr-libc-user-manual.pdf] Error 2
gmake[4]: Leaving directory '/usr/ports/devel/avr-libc/work/avr-libc-2.0.0/doc/api'
gmake[3]: *** [Makefile:377: all-recursive] Error 1
gmake[3]: Leaving directory '/usr/ports/devel/avr-libc/work/avr-libc-2.0.0/doc'
gmake[2]: *** [Makefile:432: all-recursive] Error 1
gmake[2]: Leaving directory '/usr/ports/devel/avr-libc/work/avr-libc-2.0.0'
gmake[1]: *** [Makefile:371: all] Error 2
gmake[1]: Leaving directory '/usr/ports/devel/avr-libc/work/avr-libc-2.0.0'
===> Compilation failed unexpectedly.
Comment 1 Joerg Wunsch freebsd_committer 2020-10-28 06:07:04 UTC
Please attach the refman.log file from the doc/api/latex_src/ directory within the build tree. That will give an indication about the actual error (from LaTeX).
Comment 2 alt2600 2020-10-29 02:21:51 UTC
Created attachment 219186 [details]
refman.out

https://stackoverflow.com/questions/58873054/doxygen-generated-make-bat-stops-with-errors-how-to-prevent-such-stops

I've been hunting this one down for a while trying to see if I can make sense of how this all works, but I cannot even see how latex_src generates its makefile, I don't even see it in full buildlogs, which I will attach next for more reference. but can confirm pdflatex returns a non-zero status by manually running gmake on the latex_src Makefile. I tried using pdflatex -interaction=nonstopmode refman to manually call the command used in the Makefile (might be mistyping refman's extension here) and it reported a status of 1 after the command ran. I see a log of these badness 10000 in the refman.out with overfills and underfills, but I don't know how to parse it to know whats wrong. if does spit out a PDF that seems complete, but I didn't parse each page to see if there were glitches in the output. not sure if this is a doxygen issue for being overly pedantic or what. sorry I cannot be more helpful, this is beyond my hacking skills to give any better information. let me know if you want more logs.
Comment 3 alt2600 2020-10-29 02:31:05 UTC
Created attachment 219187 [details]
build log, truncated for just document build

first call to pdflatex is line 877
Comment 4 alt2600 2020-10-29 02:32:49 UTC
sorry the full build log was too large to post so I had to truncate it down, I didn't realize until after I wrote the comment on the refman.out
Comment 5 Joerg Wunsch freebsd_committer 2020-10-29 06:22:55 UTC
OK, the evil starts here:

! LaTeX Error: File `largedemo-setup' not found.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.10 \includegraphics[width=12cm]{largedemo-setup}
                                                  
I could not locate the file with any of these extensions:
.png,.pdf,.jpg,.mps,.jpeg,.jbig2,.jb2,.PNG,.PDF,.JPG,.JPEG,.JBIG2,.JB2,.eps
Try typing  <return>  to proceed.

Can you also post a directory listing of the LaTeX directory?

Basically, this

jpegtopnm largedemo-setup.jpg |\
pnmtops -noturn -dpi 180 -equalpixels \
> largedemo-setup.eps

is what is supposed to generate this file (largedemo-setup.eps).

Problem is: in my setup, it works as expected, I cannot reproduce.
Comment 6 alt2600 2020-10-29 20:15:08 UTC
Created attachment 219208 [details]
latex_src ls output

so I looked the files seem to exist in eps and pdf, also saw in the log the wiring and wiring2 are saying are missing. so the plot thickens...

I am using
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_COLLATE=C

in my system profile. This was something I set at install long before any ports had been built/installed. I am wondering if this is something that I've run into on mostly windows where the - is replaced with a double - character somewhere along the line. not sure a quick way to check and visually it doesn't seem this way as I know usually on windows at least double dash is visually ever so slightly wider.

At one point along the line in my tests I did manually edit doxygen.config.in to set the input files as being UTF-8 after extraction, but it made no difference so I didn't mention previously.

on line 8711 this file does seem to be missing from latex_src its in
l.29 \includegraphics[width=12cm]{stdiodemo-setup}
                                                  
I could not locate the file with any of these extensions:
.png,.pdf,.jpg,.mps,.jpeg,.jbig2,.jb2,.PNG,.PDF,.JPG,.JPEG,.JBIG2,.JB2,.eps
Try typing  <return>  to proceed.
If that doesn't work, type  X <return>  to quit.

the crazy thing is the pictures are in refman.pdf, I'll post that next if its not too large
Comment 7 alt2600 2020-10-29 20:23:03 UTC
its 1.4 megs, don't think it will let me post the pdf, and it doesn't compress down much. just to try i reinstalled netpbm and doxygen, it made no effect
Comment 8 Joerg Wunsch freebsd_committer 2020-11-02 22:09:55 UTC
Well, I still have no idea why it's not finding these files. Your directory listing shows they are there (both, largedemo-setup.eps as well as largedemo-setup.pdf), yet your latex command fails to find them.