[Ecls-list] [PATCH] Compiler error, Windows MSVC
Juan Jose Garcia-Ripoll
juanjose.garciaripoll at googlemail.com
Wed Jan 25 11:16:39 UTC 2012
On Wed, Jan 25, 2012 at 5:56 AM, Andrew Paul <a2 at andrewpaul.com> wrote:
> With respect to the bug posted here:
> I think I have found the problem and have corrected it:
Thanks a lot for the fix, Andrew. I am a bit surprised that this did not
pop up in any of my other installations (Debian, OSX, etc). I have
committed your patch to my local repository and will upload it later on
In addition, there seems to be something wrong with asdf - when it is
> loaded, requiring a prebuilt contrib module (eg sockets) generates asdf
> errors, as it tries to handle it instead of the contrib loader.
> Error Output:
> Condition of type: FILE-ERROR
> Filesystem error with pathname #P"C:/ecl/sockets.fasc".
> 1) the file does not exist, or
> Broken at SI:BYTECODES. [Evaluation of: NIL] In: #<process TOP-LEVEL>
ASDF is confused by the fact that we have two types of compiled files:
native ones, built with a C compiler, ending in *.fas, and bytecompiled
ones, ending in *.fasc. I will upload a fix later on.
> Finally, a heads-up for anyone using a symlinked local-projects:
> write-file-date returns nil for windows symlinks (created with mklink /D )
This seems to be a problem with the runtime:
Plus I have not found the Windows functions that allow me to detect whether
a file is a symbolic link or not. Handling of these objects seems to be
very lousily specified throughout the Windows API.
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ecl-devel