Hi Peter, > > Here's the long answer: > > > > Despite your laudable attempts at recompiling with largefile support, I > > continue to believe this restriction is about compiler options and not > > anything in dvips specifically. The error message "dvips: Problems with > > file writing; probably disk full." is given upon any output error. > > There's no magic constant in dvips preventing >2gb output. > > > > .... > > > > kpathsea/common.ac used to have AC_SYS_LARGEFILE, but we no longer use > > that file. There is no AC_SYS_LARGEFILE in any current configure that I > > can see. .... > > There is AC_SYS_LARGEFILE in m4/kpse-common.m4 used by virtually each > texk/*/configure.ac. > > > I also do not know if AC_SYS_LARGEFILE by itself is > > sufficient, or if more changes to the source are necessary. > > Certainly not. At the very least you have to use fseeko/ftello/off_t. > > > In any event, as stated in Build, the relevant declarations in TeX are > > still inconsistent. That's a different (and highly nontrivial) bug. > > I think it is about time to address this problem!
I think there is no 2G limit for the output file in the present dvips even in 32bit systems. I assume dvi file, pk, eps, pfb files etc. are less than 2G. I've created on 32bit windows an output ps file sample.ps of size 3103465676 bytes by dvips -Ppdf -C5560 sample Thanks, Akira -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
