- ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Martin Schröder 19 Aug '07

19 Aug '07

2007/8/19, Philip TAYLOR <Philip-and-LeKhanh(a)royal-tunbridge-wells.org>: > Martin, it was your "rant" [1] (Hans's terminilogy) that triggered > this debate; you are the last person to be in a position to That wasn't a rant (and it was with tongue in cheek), that was a try to state a fact that David didn't make clear: That his problems (and his fix) where on Windows. This could all have been over sooner if David had given more information up front. If you want to continue this discussion, fine; but please leave ntg-pdftex out of this. Best Martin

2 1

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

18 Aug '07

fwiw, I find msys http://www.mingw.org/msys.shtml a very useful thing anytime I need to do any shell scripting on windows. Thanh On Sat, Aug 18, 2007 at 11:48:29AM +0200, David Kastrup wrote: > 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 > ) > ) > > [...]

3 2

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

18 Aug '07

On Sat, Aug 18, 2007 at 02:32:03PM +0200, David Kastrup wrote: > > [...] > > > I have written some applications that are used on both *x and > > windows. While it is possible to have a build environment on > > Windows (using Msys), it has been much easier to use a > > cross-compiler under linux, e.g., > > <http://www.stats.ox.ac.uk/pub/Rtools/>. It would be interesting to > > try using these tools to create a build-win32.sh for pdftex. > > A working cross compilation environment would help a _lot_. since the very beginning of pdftex I used to cross-compile pdftex binaries using the following cross-compilers: djgpp mingw32 gnuwin32 (and recently also gcc for linux ppc) Then I didn't need to do that anymore, so I stopped being interested in this issue. But until now I can still cross-compile at least djgpp from the latest pdftex sources. However I heard from Hans that djgpp binaries are not that fast as those compiled by mingw32. IIRC Taco is using mingw32 to build luatex binaries for windows, so he may have more useful input. Anyway, if anyone needs djgpp binaries of pdftex, I can make that immediately. Thanh

1 0

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: > David Kastrup wrote: > >> Have you actually programmed any serious batch scripts under Windows? > > Yes, many : after leaving VMS (a forced migration, not my choice) > I have worked only with Windows. Probably the key to success > is a familiarity with the HELP system : > >> In addition, substitution of FOR variable references has been enhanced. >> You can now use the following optional syntax: >> >> %~I - expands %I removing any surrounding quotes (") >> %~fI - expands %I to a fully qualified path name >> %~dI - expands %I to a drive letter only >> %~pI - expands %I to a path only >> %~nI - expands %I to a file name only >> %~xI - expands %I to a file extension only >> %~sI - expanded path contains short names only >> %~aI - expands %I to file attributes of file >> %~tI - expands %I to date/time of file >> %~zI - expands %I to size of file >> %~$PATH:I - searches the directories listed in the PATH >> environment variable and expands %I to the >> fully qualified name of the first one found. >> If the environment variable name is not >> defined or the file is not found by the >> search, then this modifier expands to the >> empty string >> >> The modifiers can be combined to get compound results: >> >> %~dpI - expands %I to a drive letter and path only >> %~nxI - expands %I to a file name and extension only >> %~fsI - expands %I to a full path name with short names only >> %~dp$PATH:I - searches the directories listed in the PATH >> environment variable for %I and expands to the >> drive letter and path of the first one found. >> %~ftzaI - expands %I to a DIR like output line >> >> In the above examples %I and PATH can be replaced by other valid >> values. The %~ syntax is terminated by a valid FOR variable name. >> Picking upper case variable names like %I makes it more readable and >> avoids confusion with the modifiers, which are not case sensitive. It must be mentioned that one actually needs single-iteration for-loops for almost any useful variable manipulation. Quite intuitive. > Also very useful is Log Parser 2.2 (which does far far more than > parsing log files !) and, of course, Perl. Perl is not exactly creditable to Windows now, is it? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

1 0

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 15 Aug '07

15 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