From: Jens Doll <jd@cococo.de>
Hello,
being over several hurdles now, the Cygwin on WinXP (downloaded on March
1) is still not stable. From time to time there is a crash - like the
one below. Can anyone tell me more about the messages? It emerged from a
very basic theory file (A --> A).
Jens
$ isabelle make -B
cygpath: can't convert empty path
Running HOL-Theorien ...
Browser info at
/home/Jens/.isabelle/Isabelle2011-1/browser_info/HOL/Theorien
2 [main] sh 3652 C:\CygWin\root\bin\sh.exe: *** fatal error -
internal error reading the windows environment - too many environment
variables?
HOL-Theorien FAILED
(see also
/home/Jens/.isabelle/Isabelle2011-1/heaps/polyml-5.4.0_x86-cygwin/log/HOL-Theorien)
val it = (): unit
val commit = fn: unit -> bool
Loading theory "simple"
val it = (): unit
"/home/Jens/.isabelle/Isabelle2011-1/browser_info/HOL"
*** System command failed: mkdir -p
'/home/Jens/.isabelle/Isabelle2011-1/browser_info/HOL/Theorien/outline'
IsaMakefile:25: recipe for target
`/home/Jens/.isabelle/Isabelle2011-1/heaps/polyml-5.4.0_x86-cygwin/log/HOL-Theorien.gz'
failed
make: ***
[/home/Jens/.isabelle/Isabelle2011-1/heaps/polyml-5.4.0_x86-cygwin/log/HOL-Theorien.gz]
Error 1
From: Makarius <makarius@sketis.net>
Googling for 10min reveals the following from
http://msdn.microsoft.com/en-us/library/windows/desktop/ms682653%28v=vs.85%29.aspx
The maximum size of a user-defined environment variable is 32,767
characters. There is no technical limitation on the size of the
environment block. However, there are practical limits depending on the
mechanism used to access the block. For example, a batch file cannot set a
variable that is longer than the maximum command line length.
Windows Server 2003 and Windows XP: The maximum size of the
environment block for the process is 32,767 characters. Starting with
Windows Vista and Windows Server 2008, there is no technical limitation on
the size of the environment block.
This means you either need to make sure that the total environment is less
than 32K or update to Windows 7 or similar.
Makarius
From: Jens Doll <jd@cococo.de>
Hello Makarius,
thank you for the inquiry, but it ain't that easy. From a Win XP machine
there are several ways to migrate (with a 64bit OS as target)
a) Win XP/32bit --> Win 7/32bit
b) Win XP/32bit --> Win 7/64bit
c) Win XP/32bit --> Win 7/32bit --> Win 7/64bit
d) Win XP/32bit --> Win XP/64bit --> Win 7/64bit
One problem lies in the availability of familiar packages on Win 7/64
bit. I did a) on one machine and now the LyX document processor, based
on MikTex, does not work any longer. MikTex simply does not install on
64bit Windows. MinGW does install. And also CygWin works on Win 7 and
thus Isabelle!
Regards,
Jens
From: james.isa@gmx.com
I'm using MiKTeX portable on Windows 7 64-bit, and it works:
http://miktex.org/portable/about
I'm also using LyX on Windows 7 64-bit. I have LyX set up to run
portable off of a hard drive, using the portable MiKTex. I just compiled
a document with LyX on a Windows 7 32-bit machine.
If you're doing an upgrade from WinXP to Windows 7, rather than starting
with a fresh Windows 7 install, LyX and MiKTeX could have configuration
files set up to look for files in the old XP locations rather than the
Windows 7 locations. The user document folder and application file
folders are different for Windows 7. For example, the user folder on
Windows 7 is c:\Users\your_user_name\Documents. On Windows 7 32-bit, in
addition to "C:\Program Files", there's also a "C:\Program Files (x86)".
You might already know all that. It's been a while, but when I switched
to Windows 7 and tried to use my old LyX folder with it, it seems LyX
had hard coded the WinXP file locations in its config files.
--JF
Last updated: Nov 21 2024 at 12:39 UTC