On Nov 27, 11:59 pm, Dima Pasechnik <dimp...@gmail.com> wrote: > I just checked, and saw that under Sage's ECL lisp (i.e. sage -lisp), > (pathname "") > produces an error (illegal seek) on Cygwin, while on MacOSX and Linux it's > perfectly OK.
I'd say that's a bug for ECL/Cygwin (which of the two is at fault I do not know), since the documentation clearly indicates that (pathname "") should be valid. See http://ecls.sourceforge.net/ecl/user_2.html#SEC28 However, the error you are quoting above: In function PATHNAME, the value of the only argument is NIL which is not of the expected type (OR FILE-STREAM STRING PATHNAME). indicates something else. (pathname NIL) and (pathname "") are not the same thing, so what you're seeing might be caused by yet something else. I did brew the (asdf:make-build :maxima :type :fasl :move-here ".") incantation at some point. Maxima needs to be set up with "autoconf" before this works [there may be other ways too]. Did you try to run it without the ':move here "." ' part? We can work around the move-here in some other way if that is the problem. Did you check that up to (asdf:make-build :maxima :type :fasl :move- here ".") everything works fine? [i.e., you should have a functional maxima executable] If there is an error before, then there is very little chance that asdf:make-build could ever succeed (since it'll try the same thing and fail again). That's all I can think of. We could ask Juanjo if he has some insight. It probably is a cygwin deficiency, but he is at least very familiar with the ecl internals and might know a workaround. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
