On Fri, 17 Sep 2010, Karl Berry wrote:
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;
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
On 23.09.10 Akira Kakuto (kak...@fuk.kindai.ac.jp) wrote:
Hi Peter,
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
Hi Akira,
I think there is no 2G limit for the output file in the
present dvips even in 32bit systems.
Right, as I already explained, there is no limit specifically in dvips.
I can only surmise that on w32 the compiler does 64-bit file stuff by
default. Unless you did a ton of 64-bit
tags 383781 + wontfix
stop
On 17.09.10 Karl Berry (k...@freefriends.org) wrote:
Hi Karl,
Hi Hille -- the short answer is no (as far as I can tell).
Here's the long answer:
Many thanks for the long answer.
Meanwhile, the workaround for dvips that Tom gave ages ago, as reported
in
dvips seems to have a size limit for output postscript files:
http://bugs.debian.org/383781 at least on 32bit systems. Is there any
chance to fix this?
Hi Hille -- the short answer is no (as far as I can tell).
Here's the long answer:
Despite your laudable attempts at recompiling
6 matches
Mail list logo
