<html><head></head><body>Cygwin allows you to compile linux programs on windows systems by providing the full set of Linux functions your application might expect to see. It even converts filenames into a format Linux applications are used to and therefore uses "/cygdrive/c" instead of "C:\" in pathnames.<br>Any "real" windows application that uses windows function calls for accessing files won't be able to find out where that file is supposed to be and therefore is bound to fail in that case.<br><br>Kind regards,<br><br> Gunter.<br><br><div class="gmail_quote">On November 25, 2020 6:36:40 PM GMT+01:00, Garrett Dangerfield <garrett@dangerimp.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div>I got the 20.4.24 tarball and actually managed to compile it on Windows 10 using cygwin gcc.</div><div><br></div><div>Got it to run and it seems to work pretty well from what I've seen so far.</div><div><br></div><div>However, the goal of my doing all this was to be able to link Lisp code to C/C++ code and compile-file doesn't want to work.</div><div><br></div><div>With this simple lisp file named t2.lsp:</div><div>(defun gpdtest ()<br> (print "we did it"))</div><div>When I do this (when in the same directory):</div><div>(compile-file "t2.lsp" :system-p t)</div><div>I get this back:</div><div>Condition of type: FILE-ERROR<br>Filesystem error with pathname #P"SYS:CMP.NEWEST".</div><div>Which makes no sense to me.</div><div><br></div><div>If I do this:</div><div>(probe-file "t2.lsp")</div><div>I get back:</div><div>#P"/cygdrive/c/Users/danger/gcl/t2.lsp"</div><div><br></div><div>Thoughts?</div><div><br></div><div>Apologies in advance if this is a stupid question. :-)</div><div><br></div><div>Thanks,</div><div>Garrett Dangerfield.<br></div></div>
</blockquote></div><br><div class='k9mail-signature'>-- <br>Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.</div></body></html>