Dave Cooper wrote:
Dear ASDF maintainer(s),
I just noticed that it is necessary to do
(uiop:setup-temporary-directory)
in an image which has UIOP built into it, when that image is run on a
different machine or under a different user account (at least on
Windows). Otherwise, the
I think my issue is that I am not using the UIOP image dump facility. This
is because in Allegro CL we use thei built-in excl functions like
excl:generate-application
--- it's not a matter of a generic dumplisp.
So I'm pretty sure the solution is to call the
register-image-restore-hook myself as
Dave Cooper wrote:
I think my issue is that I am not using the UIOP image dump facility.
This is because in Allegro CL we use thei built-in excl functions like
excl:generate-application --- it's not a matter of a generic dumplisp.
So I'm pretty sure the solution is to call the
On Tue, Jun 17, 2014 at 2:51 PM, Robert P. Goldman rpgold...@sift.info wrote:
Dave Cooper wrote:
I think my issue is that I am not using the UIOP image dump facility.
This is because in Allegro CL we use thei built-in excl functions like
excl:generate-application --- it's not a matter of a
Faré wrote:
On Tue, Jun 17, 2014 at 2:51 PM, Robert P. Goldman rpgold...@sift.info
wrote:
Dave Cooper wrote:
I think my issue is that I am not using the UIOP image dump facility.
This is because in Allegro CL we use thei built-in excl functions like
excl:generate-application --- it's not a
Faré wrote:
On Tue, Jun 17, 2014 at 4:33 PM, Robert P. Goldman rpgold...@sift.info
wrote:
It is probably a bug that there isn't a
uiop/stream:clear-temporary-directory
that gets registered via
uiop/configuration:register-clear-configuration-hook
in uiop/configuration. I can do it, though
On Tue, Jun 17, 2014 at 11:47 PM, Robert P. Goldman rpgold...@sift.info wrote:
clear-configuration is the function you call
when configuration files may have been modified and
you want to invalidate any current configuration loaded from them.
All it does is call the functions in the
On Mon, Jun 16, 2014 at 9:20 PM, Faré fah...@gmail.com wrote:
Interestingly, uiop/common-lisp.lisp sets
clos::*redefine-class-in-place* in uiop/common-lisp — is the problem
due to your compiling asdf/defsystem separately, and bind r-c-i-p in
LOAD, so that this setting doesn't apply to
Cher JCB,
The whole fix is in MKCL's git repo master head. I tried it on my copy
of ASDF syntax-control branch head and it worked OK. Could you
please confirm that it also works for you?
I ran
cl -l mkcl -ip :ok
which worked with both asdf 3.1.2 and the syntax-control branch,
which is