Weird Windows issue w/ pathnames

[serialhex]

Hi there, when I try to (ql:quickload '(qtools qtcore qtgui)) iI get the following err;r:

Welcome to Clozure Common Lisp Version 1.11-r16635  (WindowsX8664)!

CCL is developed and maintained by Clozure Associates. For more information
about CCL visit http://ccl.clozure.com.  To enquire about Clozure's Common Lisp
consulting services e-mail info@clozure.com or visit http://www.clozure.com.

? (ql:quickload '(qtools qtcore qtgui))
To load "qtools":
  Load 1 ASDF system:
    qtools
; Loading "qtools"
.
> Error: Can't create directory "C:/Users/538353-08/AppData/Local/cache/common-lisp/ccl-1.11-f96-win-x64/d/programmin/quicklisp/dists/quicklisp/software/qt-libs-20160208-git/libcommonqt/source/commonqt.dll/lib/commonqt.dll/lib/commonqt.dll/lib/commonqt.dll/lib/commonqt.dll/lib/commonqt.dll/".
> While executing: ENSURE-DIRECTORIES-EXIST, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.

I'm running Clozure CL 64bit, on Windows (of course). That pathname doesn't look right at all, lib/commonqt.dll/ being repeated 6 times like that is weird. Any suggestions?

Thank you in advance!

[Shinmera]

Off hand a few questions:

• Does the same happen if you only load qt-libs and nothing else?
• If so, does the problem persist if you upgrade qt-libs to the current git head?
• If not, does the problem persist if you upgrade qtools to the current git head?
• Does the same problem happen on SBCL?

I'll take a look myself later, but having answers to these should already give me some better starting points.

[serialhex]

Hmm, just (ql:quickload :qt-libs) works fine... I'm going to try some of the examples, but CCL is being a pain by not wanting to load libraries (it keeps saying they're 32-bit libs, when I'm running 64-bit CCL and want 64-bit libs -_- )

I'll try some of the examples, and I'll let you know what I get.

[Shinmera]

Note that qt-libs downloads precompiled versions of the libraries into its standalone directory. If you've loaded qt-libs or something that depends on it while running a 32x lisp implementation, the standalone directory will contain the appropriate dlls, which in turn won't work with a 64x implementation.

Otherwise it might be the case that your PATH is poisoned and it it's loading dependant dlls but for a 32x arch from somewhere that it shouldn't. qt-libs should avoid this case, but it might not be in the version you get with Quicklisp yet.

[Shinmera]

Closing for inactivity.