August 2007 - ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Akira Kakuto 18 Aug '07

18 Aug '07

Hi David, > Interesting. "Closed" with "Worksforme" because an application > accumulated file descriptors erroneously. > > The problem is that we actually _have_ this amount of outstanding > images not yet shipped out. No programming error. > > Putting the single line > > _setmaxstdio(2048); > > into web2c startup does not seem like it would be an overly onerous > complication, would it? I've confirmed that by #if defined(pdfTeX) || defined(luaTeX) _setmaxstdio(2048); #endif 2041 files in Vladimir's example are included. Probably 7 are stdin, ... etc. Best regards, Akira

7 13

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 18 Aug '07

18 Aug '07

Philip TAYLOR <Philip-and-LeKhanh(a)Royal-Tunbridge-Wells.Org> writes: > Reinhard Kotucha wrote: > >> Phil, I respect you because I know that you are an TeX expert. You >> usually know what you are talking about and you are certainly more >> familiar with TeX than anybody else. But what you said about UNIX is >> pure crap and I must admit that I'm quite disappointed. > > Well, it was intentionally provocative, but that doesn't > mean it's not grounded in truth : if you read back over > the TeX live correspondence (which is the list to which > I was referring, rather than PdfTeX or NTGTeX or whatever) > you will see over and over again questions caused by different > libraries, different compilers, different versions, different > modes of linking, etc., etc., etc. Every time I read one, > I ask myself "Why on earth do they bother ?". Because they can. So they are more noticeable than the two people who had actually managed to get it compiled under Windows. The autoconf documentation contains a section about portable shell programming: what kind of stuff you can rely on to work everywhere, and what not. It is a real horror show and a bit of a nuisance to keep everything in mind. The resulting scripts sometimes are a bit awkward. But this does not hold a candle to programming cmd.exe. Something like for i in /opt /usr/local /opt/* /usr/local/* do if test -d "$i"/software then cd "$i" subdir="$i" break fi done becomes (in a batch file, on the command line it looks different) for /D %%I in (C:\ D:\ C:\* D:\*) do ( if exist %%I\software\NUL ( %%~dI cd %%~pnI set subdir=%%I goto found ) ) :found Except that it probably won't work when you are in a subdirectory of C: or D: currently. And passing the found string into Java with "%subdir%" can cause the trailing quote to be added (because it may be backslash-preceded) into the command line argument. And if you use "echo on" in your batch file (the default), what gets echoed back at you is garbage, because Windows does not manage to treat the %%x stuff correctly when echoing. It is _much_ _much_ harder to find the necessary information for batch programming under Windows on the net, and while portability is not much of a concern, the portable subset of shell programming is still much more straightforward and usable than what cmd.exe provides. Have you actually programmed any serious batch scripts under Windows? Or are your opinions not based on working with the system? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Akira Kakuto 17 Aug '07

17 Aug '07

Hi Martin, > Let's get back to the facts: I can easily include 10000 different pdfs > on one page (and claim that the number of files is only limited by > memory) -- when \pdfximage is \immediate (which is normally is not). > This works on Linux. Does this not work on Windows? \documentclass[pdftex,a5paper]{book} \usepackage[papersize={8.5in,11in}]{geometry} \usepackage{pdfpages} % \let\mypdfximage\pdfximage \def\pdfximage{\immediate\mypdfximage} % \begin{document} \newcount\i \i=2 \loop \ifnum\i<3000 \includepdf[pages={-}]{\number\i.pdf}% \advance\i by1 \repeat \end{document} works also on Windows. The "immediate" version does not depend on the limitation on the number of open files. Thanks, Akira

1 0

Runtime limitations on open files?
by David Kastrup 17 Aug '07

17 Aug '07

Hi, we are crashing with "too many open files" on PDFTeX from TeXlive. The object id where this happens is 513 or so, and it would be my guess that PDFTeX keeps image files open as long as it has not yet shipped them out. It would appear that the system limitations of win32 are much larger, so I suspect the runtime with which TeXlive2007 has been compiled. Does anybody have a good pointer to where I might look for further information? This is quite a bad roadblock for us. -- David Kastrup

6 10

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 17 Aug '07

17 Aug '07

Jonathan Kew <jonathan_kew(a)sil.org> writes: > On 17 Aug 2007, at 12:00 pm, David Kastrup wrote: > >> we are crashing with "too many open files" on PDFTeX from TeXlive. >> The object id where this happens is 513 or so, and it would be my >> guess that PDFTeX keeps image files open as long as it has not yet >> shipped them out. >> >> It would appear that the system limitations of win32 are much larger, >> so I suspect the runtime with which TeXlive2007 has been compiled. >> >> Does anybody have a good pointer to where I might look for further >> information? This is quite a bad roadblock for us. > > I believe the W32 binaries in TL were built by Akira using MS Visual > Studio tools, but I don't know whether/how this limit can be > controlled there. See other mail on this: it would appear to be easy to fix this (namely: bump the number to 2048) in the sources. > As a workaround, have you tried alternatives such as generating DVI > output and then running dvipdfmx? It's possible that might handle > things differently. Far too many PDFTeX specific features in use, I am afraid. That road is not open to us at the moment. -- David Kastrup

1 0

[ pdftex-Bugs-856 ] build.sh can't handle pathnames with spaces
by noreply＠sarovar.org 14 Aug '07

14 Aug '07

Bugs item #856, was opened at 2007-08-14 09:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106 Category: Build process Group: v1.40.4 Status: Open >Resolution: Postponed Priority: 5 Submitted By: Francky Leyn (leyn) Assigned to: Martin Schröder (oneiros) Summary: build.sh can't handle pathnames with spaces Initial Comment: Dear, I want to compile pdftex for cygwin. I untarred the distribution in /cygdrive/c/Document and Settings/Francky Leyn/My Documents/LaTeX leyn@newyork ~/LaTeX/pdftex-1.40.5 $ ./build.sh ... build.sh stops with the following error: configure: error: can not run /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file exists and is executable: $ ls -lh "/cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub" -rwx------+ 1 leyn None 32K Jul 31 19:00 /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file /cygdrive/c/Documents doesn't exist of course and that is why buid.sh stops its execution. Could the scripts be modified so that they can handle spaces? Best regards, Francky Leyn ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-08-15 01:52 Message: Logged In: YES user_id=421 I'm sorry, but fixing this needs a change in the whole autofoo system of TL, which is not likely to happen soon. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-08-14 10:50 Message: Logged In: YES user_id=421 This needs a new configure script; I've pushed this upstream (to TeXlive). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106

1 0

[ pdftex-Bugs-856 ] build.sh can't handle pathnames with spaces
by noreply＠sarovar.org 14 Aug '07

14 Aug '07

Bugs item #856, was opened at 2007-08-14 09:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106 Category: Build process >Group: v1.40.4 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Francky Leyn (leyn) Assigned to: Martin Schröder (oneiros) Summary: build.sh can't handle pathnames with spaces Initial Comment: Dear, I want to compile pdftex for cygwin. I untarred the distribution in /cygdrive/c/Document and Settings/Francky Leyn/My Documents/LaTeX leyn@newyork ~/LaTeX/pdftex-1.40.5 $ ./build.sh ... build.sh stops with the following error: configure: error: can not run /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file exists and is executable: $ ls -lh "/cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub" -rwx------+ 1 leyn None 32K Jul 31 19:00 /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file /cygdrive/c/Documents doesn't exist of course and that is why buid.sh stops its execution. Could the scripts be modified so that they can handle spaces? Best regards, Francky Leyn ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-08-14 10:50 Message: Logged In: YES user_id=421 This needs a new configure script; I've pushed this upstream (to TeXlive). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106

1 0

[ pdftex-Bugs-856 ] build.sh can't handle pathnames with spaces
by noreply＠sarovar.org 14 Aug '07

14 Aug '07

Bugs item #856, was opened at 2007-08-14 09:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106 Category: Build process Group: None Status: Open Resolution: None Priority: 5 Submitted By: Francky Leyn (leyn) Assigned to: Martin Schröder (oneiros) Summary: build.sh can't handle pathnames with spaces Initial Comment: Dear, I want to compile pdftex for cygwin. I untarred the distribution in /cygdrive/c/Document and Settings/Francky Leyn/My Documents/LaTeX leyn@newyork ~/LaTeX/pdftex-1.40.5 $ ./build.sh ... build.sh stops with the following error: configure: error: can not run /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file exists and is executable: $ ls -lh "/cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub" -rwx------+ 1 leyn None 32K Jul 31 19:00 /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file /cygdrive/c/Documents doesn't exist of course and that is why buid.sh stops its execution. Could the scripts be modified so that they can handle spaces? Best regards, Francky Leyn ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106

1 0

[ pdftex-Patches-474 ] Use dynamically linked poppler library instead of xpdf code
by noreply＠sarovar.org 12 Aug '07

12 Aug '07

Patches item #474, was opened at 2006-01-30 17:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=474&group_id=106 Category: PDF inclusion Group: v1.30.0 Status: Open >Resolution: Accepted Priority: 6 Submitted By: Frank Küster (frank) Assigned to: Martin Schröder (oneiros) Summary: Use dynamically linked poppler library instead of xpdf code Initial Comment: This has already been applied and tested in Debian and Ubuntu, but we suggest to apply it upstream. There are a few things to do, however, as Martin already pointed out to me in a private mail. I paraphrase the main points: - the pdftex distribution should not ship libpoppler. Instead it should be possible to switch from xpdf to libpoppler using autoconf magic, if libpoppler headers are installed. This needs some coding work - We need a common API for xpdf and poppler. This is the tricky part, because the very reason for poppler's existence is that the xpdf developer, Derek Noonburg, refuses any patches that would lead to a shared library. As Martin said, "for the beginning, a header file with a couple of #ifdef'ed definitions should be enough". I'm going to subscribe to the pdftex devel list soon, but am not yet subscribed currently. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-08-10 15:40 Message: Logged In: YES user_id=421 HEAD (r228) has now a layer between pdftex and xpdf. Please comment. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-05-08 18:54 Message: Logged In: YES user_id=421 Just an update: SUSE has also started switching to poppler. My idea is to first add an abstraction layer for xpdf/poppler/... and then add the autofoo stuff. ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-08-14 21:20 Message: Logged In: YES user_id=3360 Hi Martin, this is clearly post-1.40, I agree. I have not worked on any autofoo stuff, and I won't be able to do that soon (instead, I try to integrate pdftex-1.40 into teTeX 3.0 which proved to be non-trivial). Regards, Frank ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-08-13 22:02 Message: Logged In: YES user_id=421 Frank, have you done any further work on this? I just had a first look at integrating poppler and see a very different use of configure... :-{ Also your diff only patches the sources, but not the autofoo-stuff. What I want is: - a distribution of poppler in src/libs, which can be used instead of xpdf - a way to switch bewteen xpdf and poppler via configure - for poppler to be able to switch between static and dynamic via configure - and finally, a header file abstracting poppler/xpdf would be nice, but is not really needed, as poppler/xpdf are only used by two source files. Best Martin ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-02-13 08:58 Message: Logged In: YES user_id=3360 I agree that this is something to think over and check very well, so better not push it into 1.40. But I'd appreciate if someone could answer my mail to ntg-pdftex regarding the autoconf setup in pdftex, or if you could tell me whom to ask specifically if nobody among the active developers knows about it. See you in Berlin, Frank ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-02-13 01:50 Message: Logged In: YES user_id=421 I've attached the patch by Frank from http://www.ntg.nl/pipermail/ntg-pdftex/2006-February/001993.html ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-02-13 01:46 Message: Logged In: YES user_id=421 This is too late for 1.40, so I'll postpone it. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=474&group_id=106

3 2

make depend :-(
by Martin Schröder 10 Aug '07

10 Aug '07

Hi, I just tried a "make depend" in pdftexdir and found it broken; and my knowlegde of make/sh/grep/sed/autofoo/... is not sufficient to fix it. If some kind soul here could fix it, I'd be grateful. Best Martin PS: And "make depend" in libs/xpdf/xpdf is also not producing the expected result... :-(

1 0