Closed krrrcks closed 10 years ago
Do you get this problem if you build buildapp from the command line with make LISP=ccl
?
I should be able to look at this bug more closely towards the end of the week.
Acutally I came across this bug with the "make LISP=ccl". Here is my output:
make LISP=ccl ccl --quiet --no-init \ --eval "(require 'asdf)" \ --eval "(push \"$(pwd)/\" asdf:central-registry)" \ --eval "(require 'buildapp)" \ --eval "(buildapp::build-buildapp)" \ --eval "#+sbcl (exit) #+ccl (quit)" Fatal SIMPLE-FILE-ERROR: Permission denied : "/buildapp" Error: Permission denied : "/buildapp" While executing: CCL::%CREATE-FILE, in process listener(1). Type :GO to continue, :POP to abort, :R for a list of available restarts.> If continued: Skip loading "/home/dbr/sw/buildapp/dumper-f0dIhgSY.lisp" Type :? for other options. 1 >
It seems that the problem arose because in native-namestring default-pathname-defaults is bound to #P"/"?
I don't see this problem in my version of ccl
(Version 1.9-r15756 (LinuxX8632)
), but I also don't see the need for the let-binding of default-pathname-defaults in native-namestring (which I had cribbed from asdf thinking it served some purpose). I just pushed up db334d1b in my fork of buildapp which should fix this problem.
Thanks for reporting the error and pointing out the source of the problem. If this fixes things for you I think it should be applied to the main buildapp repo.
I tested with Version 1.9-dev-r15288M (LinuxX8664). The patch fixes the issue! Thanks for adding the ccl support! I appreciate that very much.
Resolved for a while now.
I tested building buildapp on CCL and it failed with "Permission denied: '/buildapp'". Complete output here: http://paste.lisp.org/display/138728
To me it seems that NATIVE-NAMESTRING binds default-pathname-defaults to #P"/".