Jean-Claude Beaudoin wrote:
I think I just found out the environmental discrepancy between your setup and mine. test-program.script depends on system :lisp-invocation from XCVB and will happily skip over the whole test if that demand is not satisfied. XCVB is not currently part of my readily available configuration. Thus nothing shows up on my side when I test ASDF.
In a patch I provided to you to port ASDF 3.0.3 to MKCL and that you applied on 2014-03-17, I submitted in test-program.script a way to run the test without that "XCVB/lisp-invocation" dependency but that code got removed by the commit applied right after yours.
Currently test-program.script seems to be the only test requiring XCVB. Is this requirement really worth the overhead it imposes?
Actually, we pulled lisp-invocation into ASDF as a git submodule (it was liberated from XCVB). You should get this lisp invocation automatically.
Please go to your ext/ subdirectory and populate the git submodules there, and try again.
Thanks! r
On Mon, Nov 3, 2014 at 11:28 PM, Robert P. Goldman rpgoldman@sift.info wrote:
Actually, we pulled lisp-invocation into ASDF as a git submodule (it was liberated from XCVB). You should get this lisp invocation automatically.
Please go to your ext/ subdirectory and populate the git submodules there, and try again.
I had to manually do "git submodule update --init" in my ASDF "fresh" repo clone directory in order to get anything in the ./ext/ directory populated. It doesn't seem to trigger on its own from the Makefile.
Now having done so I do get the "hanging" behavior in test-program.script. It looks like my stuff gets into some kind of busy wait loop and remains stuck there. I will investigate some more and get back to you with the fix, most probably in the coming days.
Thanks,
JCB
-
Jean-Claude Beaudoin -
Robert P. Goldman