Attached please find a patch synchronizing the version of ASDF we intend to ship with abcl-1.1.0 with the canonical version.
These changes deal with bugs when using systems contained in jar archives via the ABCL implementation specific extension of CL:PATHNAME.
On Wed, Nov 28, 2012 at 6:28 AM, Mark Evenson evenson@panix.com wrote:
Attached please find a patch synchronizing the version of ASDF we intend to ship with abcl-1.1.0 with the canonical version.
These changes deal with bugs when using systems contained in jar archives via the ABCL implementation specific extension of CL:PATHNAME.
I've merged something based on it into asdf 2.26.3.
Can you test it, and maybe ship it instead of your locally patched version, assuming I haven't release 2.27 yet?
Also, should your (find :windows *features*) actually be (os-windows-p) ? Note the subtle semantic different, where we consider it not windows if it's cygwin or other unix-on-windows environment. That may or may not apply to ABCL.
BTW, when you locally patch, I recommend you use names such as 2.26.0.1; see explanations inside asdf.lisp.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Passive hope is wishful thinking, a poison of the mind. Active hope is creative passion, the mover of the universe.
On 11/29/12 3:29 PM, Faré wrote:
On Wed, Nov 28, 2012 at 6:28 AM, Mark Evenson evenson@panix.com wrote:
Attached please find a patch synchronizing the version of ASDF we intend to ship with abcl-1.1.0 with the canonical version.
These changes deal with bugs when using systems contained in jar archives via the ABCL implementation specific extension of CL:PATHNAME.
I've merged something based on it into asdf 2.26.3.
Can you test it, and maybe ship it instead of your locally patched version, assuming I haven't release 2.27 yet?
The abcl build process is rather strict, exiting with failure if the compilation emits warnings.
Could you possible push the attached patch to eliminate the warning, and I'll grab the resulting code?
Also, should your (find :windows *features*) actually be (os-windows-p) ? Note the subtle semantic different, where we consider it not windows if it's cygwin or other unix-on-windows environment. That may or may not apply to ABCL.
About the only way I can be convinced to use Windows is from Cygwin, so #+abcl code in asdf.lisp has been tested as working under cygwin. As far as I understand things, since the JVM is a Windows executable that can be invoked outside of cygwin, even if abcl is invoked under cygwin it will still manipulate file paths like a Windows process. When I get a chance, I will study the usage of OS-WINDOWS-P to make sure that I am not missing something here.
BTW, when you locally patch, I recommend you use names such as 2.26.0.1; see explanations inside asdf.lisp.
Duly noted.
On Thu, Nov 29, 2012 at 2:52 PM, Mark Evenson evenson@panix.com wrote:
The abcl build process is rather strict, exiting with failure if the compilation emits warnings.
Could you possible push the attached patch to eliminate the warning, and I'll grab the resulting code?
Yes, I also found this bug and previously committed it as 2.26.4. I've also pushed a fix for CMUCL upgrade as 2.26.5. Can you test the latest ASDF and see if it works for you?
When I get a chance, I will study the usage of OS-WINDOWS-P to make sure that I am not missing something here.
Thanks a lot. Note that if OS-WINDOWS-P fails in this case, it probably also fails in other cases.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Personal dishonesty is not needed to produce a dishonest business plan or research proposal. Wishful thinking suffices. — John McCarthy
-
Faré -
Mark Evenson