On Sun 2016-02-21 05:12:49 -0800, Andreas Metzler wrote: > I have now merged/selectively pulled the necessary changes on the > experimental branch. Builds-for-me. Could you take a look?
hm, nope, i'm actually seeing an error on the experimental branch with the texlive compilation: ----- [72] [73] [74] [75] [76] [77] [78] Chapter 13 [79] [80] Chapter 14 [81] [82] [83] Chapter 15 [84] Chapter 16 [85] [86] /home/dkg/src/libgcrypt/libgcrypt20/doc/gcrypt.texi:5312: Could not find image file libgcrypt-modules for pdf. @dopdfimage ...uld not find image file #1 for pdf} @else @gdef @pdfimgext {JP... @imagexxx ...t @fi @ifpdf @dopdfimage {#1}{#2}{#3} @else @ifx @XeTeXrevision ... @image ...true @fi @else @imagexxx #1,,,,,@finish @fi <argument> ...odules, 150mm,,Libgcrypt subsystems} @unskip @hfil @centersub ...enalty @fi @line {@kern @leftskip #1 @kern @rightskip } @\center ...{@hfil @ignorespaces #1@unskip @hfil } @let @centersub @relax l.5312 ...pt-modules, 150mm,,Libgcrypt subsystems} !pdfTeX error: pdfetex (file libgcrypt-modules.): cannot find image file ==> Fatal error occurred, no output PDF file produced! ---- But i did just upgrade texlive on this build system to 2015.20160215-1, so maybe that's at fault? I'm pretty sure this isn't related to the windows cross-build process. Are you seeing the same thing with this version of texlive-latex-base? > What is still open is whether we need to ship the la files at all, and > if we do whether they really should have non-empty dep-libs. I think i don't need them for my purposes. if you want to go ahead without them, i'm happy to let you know (presumably via the BTS) if it turns out that i do need em for whatever reason. thanks for your prompt work on this, and your investigations! --dkg