ABCL is special in that it can run on either Windows or Unix.
The problem is that ASDF 2.017 determines which of Windows or Unix at compile-time, which causes confusion when ABCL's builtin ASDF is compiled on Windows and used on Unix or vice-versa. And I can tell your binary was definitely produced on Windows.
(I found this issue while testing cl-launch. I also noticed that you fixed your ext:*command-line-argument-list* albeit in a necessarily incompatible way.)
I suppose the solution is that the test of unixness vs windowsness should happen at runtime. Crazy.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
I suppose the solution is that the test of unixness vs windowsness should happen at runtime. Crazy.
I doubt whether, what is exists other solution ... (
P.S. And yet, the separation of the files (and joining them into one, when do make) - seems convenient. For example, to encapsulate all the platform-dependent parts in a separate file - it would be nice.
Чтв 20 Окт 2011 20:01:54 +0400, Far fahree@gmail.com написал:
ABCL is special in that it can run on either Windows or Unix.
The problem is that ASDF 2.017 determines which of Windows or Unix at compile-time, which causes confusion when ABCL's builtin ASDF is compiled on Windows and used on Unix or vice-versa. And I can tell your binary was definitely produced on Windows.
(I found this issue while testing cl-launch. I also noticed that you fixed your ext:*command-line-argument-list* albeit in a necessarily incompatible way.)
I suppose the solution is that the test of unixness vs windowsness should happen at runtime. Crazy.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On Oct 20, 2011, at 18:00 , Faré wrote:
ABCL is special in that it can run on either Windows or Unix.
The problem is that ASDF 2.017 determines which of Windows or Unix at compile-time, which causes confusion when ABCL's builtin ASDF is compiled on Windows and used on Unix or vice-versa. And I can tell your binary was definitely produced on Windows.
(I found this issue while testing cl-launch. I also noticed that you fixed your ext:*command-line-argument-list* albeit in a necessarily incompatible way.)
I suppose the solution is that the test of unixness vs windowsness should happen at runtime. Crazy.
We place :WINDOWS and :UNIX in *FEATURES* depending on where we end up executing, so forms like
(when (find :unix *features*) (run-process "ls"))
should do the right sorts of things. If you have other suggestions about how to manage this, please make them.
Mark evenson@panix.com
I suppose the solution is that the test of unixness vs windowsness should happen at runtime. Crazy.
We place :WINDOWS and :UNIX in *FEATURES* depending on where we end up executing, so forms like
(when (find :unix *features*) (run-process "ls"))
should do the right sorts of things. If you have other suggestions about how to manage this, please make them.
You're doing the right thing. I suppose you're also doing some magic to properly parse C:\foo\bar\ on Windows and /c/foo/bar on Unix.
ASDF just wasn't prepared to that (and neither was XCVB). Please test 2.017.22, I'd like to release it as 2.018, at the end of the month.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org No man would listen to you talk if he didn't know it was his turn next. — Edgar Watson Howe
-
Faré -
Mark Evenson -
Сергей Катревич