Dear ASDF users, unless you have requests for urgent bugs and/or object to some of the changes I just made (see below), I intend to release 2.013 later this week. Changes since 2.012: * cleanup in use of features. Introducing #+asdf-unix and #+asdf-window. (2.012.1) * cleanup in support for clisp. Implementation identifier vs processor name (2.012.2) * support for Digitool's legacy system (R)MCL (2.012.3) - as requested by p-cos to test his library. * cleanup when using portable pathnames (2.012.4) * cleanup in support for ECL (2.012.5, 2.012.6) * parse the pathname of a defsystem portably when it's a string. (2.012.7) * support for Symbolics' legacy system Genera (2.012.8) - proof of concept, completes legacy support and allowed me to test my libraries. * support for .. as :back in our portable pseudo-namestring language and in merge-pathnames* - should make quite a few pathnames things less ugly. (2.012.8) * Remember source-registry and output-translations parameters (2.012.8) - should provide a portable solution to the need many people have expressed to be able to tweak a configuration after the fact. * some documentation updates Possibly questionable change: * To support Genera, I removed ~@< from our error message format strings. Frankly, I think cuteness matters that much when printing error. Feedback requested: * are the (currently unexported) variables *source-registry-parameter* and *output-translations-parameter* acceptable APIs for reconfigurability of ASDF? If so, I'll export them before release. If not, I'd appreciate API proposals, if possible from people who understand how current code works. ASDF is pretty stable, and we're really polishing corner cases, but also making some [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Give up all hope for a better yesterday, even a better just now. Never give up hope for a better tomorrow. — Patri Friedman
* To support Genera, I removed ~@< from our error message format strings. Frankly, I think cuteness matters that much when printing error.
At least few of those messages could benefit from forced newlines as an alternative. When running Slime in ~80 character frame error message wrapping can be a real usability issue -- impacting many more people than availability of Genera support. :) Cheers, -- Nikodemus
On 14 March 2011 10:14, Nikodemus Siivola <nikodemus@random-state.net> wrote:
* To support Genera, I removed ~@< from our error message format strings. Frankly, I think cuteness matters that much when printing error.
At least few of those messages could benefit from forced newlines as an alternative. When running Slime in ~80 character frame error message wrapping can be a real usability issue -- impacting many more people than availability of Genera support. :)
You're probably right. Or some #. wrapper to add ~@< ~> around a few of the strings. I'll accept a patch and/or a request for change in some specific format strings. Use git show 2.012.8 to see which strings were affected. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Property in ideas is an insoluble contradiction. [He who complains of "theft" of his idea] complains that something has been stolen which he still possesses, and he wants back something which, if given to him a thousand times, would add nothing to his possession. — H. Rentzsch, Geistiges Eigenthum, 1866.
Faré <fahree@gmail.com> writes:
Dear ASDF users,
unless you have requests for urgent bugs and/or object to some of the changes I just made (see below), I intend to release 2.013 later this week.
Hi, I have a problem loading SB-POSIX when using the latest asdf from git that doesn't seem to happen with 2.012. Here's how I trigger it: sbcl --no-userinit --no-sysinit --disable-debugger \ --load asdf.lisp --eval "(require 'sb-posix)" \ --eval "(sb-ext:quit)" Produces this: This is SBCL 1.0.46, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ; in: LAMBDA NIL ; (ASDF::CONDITION-ARGUMENTS ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-ARGUMENTS ; (ASDF::CONDITION-FORM ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-FORM ; (ASDF::CONDITION-FORMAT ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-FORMAT ; (ASDF::CONDITION-LOCATION ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-LOCATION ; ; compilation unit finished ; Undefined functions: ; CONDITION-ARGUMENTS CONDITION-FORM CONDITION-FORMAT CONDITION-LOCATION ; caught 4 STYLE-WARNING conditions ; (ASDF:COERCE-NAME (ASDF::MISSING-PARENT ASDF::C)) ; ; caught STYLE-WARNING: ; undefined function: COERCE-NAME ; ; compilation unit finished ; Undefined function: ; COERCE-NAME ; caught 1 STYLE-WARNING condition ; Loading system definition from /usr/local/lib/sbcl/sb-grovel/sb-grovel.asd into #<PACKAGE "ASDF1"> ; Registering #<SYSTEM SB-GROVEL> as SB-GROVEL (/usr/local/lib/sbcl/sb-posix/constants.lisp /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.fasl /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.fasl /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/foo.c /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/a.out /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp) ASDF could not load sb-posix because failed to find the TRUENAME of /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp: No such file or directory. unhandled SB-INT:SIMPLE-FILE-ERROR in thread #<SB-THREAD:THREAD "initial thread" RUNNING {10029417C1}>: failed to find the TRUENAME of /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp: No such file or directory 0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {10034F7029}> :START 0 :COUNT 128) 1: (BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {10001676D1}>) 2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SB-INT:SIMPLE-FILE-ERROR "~@<~?: ~2I~_~A~:>" {10034F20F1}> #<unavailable argument>) 3: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<SB-INT:SIMPLE-FILE-ERROR "~@<~?: ~2I~_~A~:>" {10034F20F1}>) 4: (INVOKE-DEBUGGER #<SB-INT:SIMPLE-FILE-ERROR "~@<~?: ~2I~_~A~:>" {10034F20F1}>) 5: (ERROR SB-INT:SIMPLE-FILE-ERROR :PATHNAME #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" :FORMAT-CONTROL "~@<~?: ~2I~_~A~:>" :FORMAT-ARGUMENTS ("failed to find the TRUENAME of ~A" (#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp") "No such file or directory")) 6: (SB-IMPL::SIMPLE-FILE-PERROR "failed to find the TRUENAME of ~A" #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" 2) 7: ((FLET SB-IMPL::FAIL) "failed to find the TRUENAME of ~A" #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" 2) 8: (SB-IMPL::QUERY-FILE-SYSTEM #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" :TRUENAME T) 9: (TRUENAME #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp") 10: ((FLET SB-C::TRY-WITH-TYPE) #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" "lisp" T) 11: (SB-C::VERIFY-SOURCE-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp") 12: (SB-C::VERIFY-SOURCE-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp")[:EXTERNAL] 13: (COMPILE-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" :OUTPUT-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.fasl" :VERBOSE NIL :PRINT NIL :EXTERNAL-FORMAT :DEFAULT :TRACE-FILE NIL :BLOCK-COMPILE NIL :EMIT-CFASL NIL) 14: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP SB-GROVEL:GROVEL-CONSTANTS-FILE)) #<unavailable argument> #<unavailable argument> #<ASDF:COMPILE-OP NIL {1003A5CEC1}> #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) 15: ((SB-PCL::EMF ASDF:PERFORM) #<unavailable argument> #<unavailable argument> #<ASDF:COMPILE-OP NIL {1003A5CEC1}> #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) 16: ((SB-PCL::FAST-METHOD ASDF::PERFORM-WITH-RESTARTS (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) #<ASDF:COMPILE-OP NIL {1003A5CEC1}> #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) 17: ((LAMBDA ())) 18: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) 19: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]324)) 20: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FFFF6D5F529}> #S(SB-THREAD:MUTEX :NAME "World Lock" :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {10029417C1}> :STATE 1)) 21: ((FLET SB-C::WITH-IT)) 22: ((SB-PCL::FAST-METHOD ASDF:OPERATE (T T)) #<unused argument> #<unused argument> ASDF:LOAD-OP #<ASDF:SYSTEM "sb-posix">) 23: ((SB-PCL::EMF ASDF:OPERATE) #<unused argument> #<unused argument> ASDF:LOAD-OP #<ASDF:SYSTEM "sb-posix"> 17592166825703 0) 24: (ASDF:LOAD-SYSTEM #<ASDF:SYSTEM "sb-posix">) 25: (ASDF::MODULE-PROVIDE-ASDF SB-POSIX) 26: ((LAMBDA (#:G[REQUIRE]13)) ASDF::MODULE-PROVIDE-ASDF) 27: (SB-IMPL::%MAP-FOR-EFFECT-ARITY-1 #<CLOSURE (LAMBDA #) {1003275809}> (ASDF::MODULE-PROVIDE-ASDF SB-IMPL::MODULE-PROVIDE-CONTRIB)) 28: (REQUIRE SB-POSIX NIL) 29: (SB-INT:SIMPLE-EVAL-IN-LEXENV (REQUIRE 'SB-POSIX) #<NULL-LEXENV>) 30: (SB-IMPL::PROCESS-EVAL/LOAD-OPTIONS ((:LOAD . "asdf.lisp") (:EVAL . "(require 'sb-posix)") (:EVAL . "(quit)"))) 31: (SB-IMPL::TOPLEVEL-INIT) 32: ((LABELS SB-IMPL::RESTART-LISP)) unhandled condition in --disable-debugger mode, quitting ; ; compilation unit aborted ; caught 1 fatal ERROR condition The same thing works fine in ASDF 2.012. What should I do? Also, I use the unexported MISSING-REQUIRES and MISSING-REQUIRED-BY to do autoloading of missing system components. Is there any chance they'll become an exported supported interface in the next version? Zach
Ouch, I might have messed up with the SBCL_HOME treatment of 2.012.9. Do you get the same behavior in 2.012.8? Can you tell me the values of the following *source-registry* *output-translations* (getenv "SBCL_HOME") [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] There are two types of people in the world: People who think there are two kinds of people, and people who don't. On 16 March 2011 23:57, Zach Beane <xach@xach.com> wrote:
Faré <fahree@gmail.com> writes:
Dear ASDF users,
unless you have requests for urgent bugs and/or object to some of the changes I just made (see below), I intend to release 2.013 later this week.
Hi,
I have a problem loading SB-POSIX when using the latest asdf from git that doesn't seem to happen with 2.012. Here's how I trigger it:
sbcl --no-userinit --no-sysinit --disable-debugger \ --load asdf.lisp --eval "(require 'sb-posix)" \ --eval "(sb-ext:quit)"
Produces this:
This is SBCL 1.0.46, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>.
SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information.
; in: LAMBDA NIL ; (ASDF::CONDITION-ARGUMENTS ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-ARGUMENTS
; (ASDF::CONDITION-FORM ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-FORM
; (ASDF::CONDITION-FORMAT ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-FORMAT
; (ASDF::CONDITION-LOCATION ASDF::C) ; ; caught STYLE-WARNING: ; undefined function: CONDITION-LOCATION ; ; compilation unit finished ; Undefined functions: ; CONDITION-ARGUMENTS CONDITION-FORM CONDITION-FORMAT CONDITION-LOCATION ; caught 4 STYLE-WARNING conditions
; (ASDF:COERCE-NAME (ASDF::MISSING-PARENT ASDF::C)) ; ; caught STYLE-WARNING: ; undefined function: COERCE-NAME ; ; compilation unit finished ; Undefined function: ; COERCE-NAME ; caught 1 STYLE-WARNING condition ; Loading system definition from /usr/local/lib/sbcl/sb-grovel/sb-grovel.asd into #<PACKAGE "ASDF1"> ; Registering #<SYSTEM SB-GROVEL> as SB-GROVEL (/usr/local/lib/sbcl/sb-posix/constants.lisp /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.fasl /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.fasl /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/foo.c /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/a.out /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp) ASDF could not load sb-posix because failed to find the TRUENAME of /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp: No such file or directory. unhandled SB-INT:SIMPLE-FILE-ERROR in thread #<SB-THREAD:THREAD "initial thread" RUNNING {10029417C1}>: failed to find the TRUENAME of /home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp: No such file or directory
0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {10034F7029}> :START 0 :COUNT 128) 1: (BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {10001676D1}>) 2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SB-INT:SIMPLE-FILE-ERROR "~@<~?: ~2I~_~A~:>" {10034F20F1}> #<unavailable argument>) 3: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<SB-INT:SIMPLE-FILE-ERROR "~@<~?: ~2I~_~A~:>" {10034F20F1}>) 4: (INVOKE-DEBUGGER #<SB-INT:SIMPLE-FILE-ERROR "~@<~?: ~2I~_~A~:>" {10034F20F1}>) 5: (ERROR SB-INT:SIMPLE-FILE-ERROR :PATHNAME #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" :FORMAT-CONTROL "~@<~?: ~2I~_~A~:>" :FORMAT-ARGUMENTS ("failed to find the TRUENAME of ~A" (#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp") "No such file or directory")) 6: (SB-IMPL::SIMPLE-FILE-PERROR "failed to find the TRUENAME of ~A" #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" 2) 7: ((FLET SB-IMPL::FAIL) "failed to find the TRUENAME of ~A" #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" 2) 8: (SB-IMPL::QUERY-FILE-SYSTEM #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" :TRUENAME T) 9: (TRUENAME #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp") 10: ((FLET SB-C::TRY-WITH-TYPE) #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" "lisp" T) 11: (SB-C::VERIFY-SOURCE-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp") 12: (SB-C::VERIFY-SOURCE-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp")[:EXTERNAL] 13: (COMPILE-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.lisp-temp" :OUTPUT-FILE #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/usr/local/lib/sbcl/sb-posix/constants.fasl" :VERBOSE NIL :PRINT NIL :EXTERNAL-FORMAT :DEFAULT :TRACE-FILE NIL :BLOCK-COMPILE NIL :EMIT-CFASL NIL) 14: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP SB-GROVEL:GROVEL-CONSTANTS-FILE)) #<unavailable argument> #<unavailable argument> #<ASDF:COMPILE-OP NIL {1003A5CEC1}> #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) 15: ((SB-PCL::EMF ASDF:PERFORM) #<unavailable argument> #<unavailable argument> #<ASDF:COMPILE-OP NIL {1003A5CEC1}> #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) 16: ((SB-PCL::FAST-METHOD ASDF::PERFORM-WITH-RESTARTS (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) #<ASDF:COMPILE-OP NIL {1003A5CEC1}> #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) 17: ((LAMBDA ())) 18: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) 19: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]324)) 20: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FFFF6D5F529}> #S(SB-THREAD:MUTEX :NAME "World Lock" :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {10029417C1}> :STATE 1)) 21: ((FLET SB-C::WITH-IT)) 22: ((SB-PCL::FAST-METHOD ASDF:OPERATE (T T)) #<unused argument> #<unused argument> ASDF:LOAD-OP #<ASDF:SYSTEM "sb-posix">) 23: ((SB-PCL::EMF ASDF:OPERATE) #<unused argument> #<unused argument> ASDF:LOAD-OP #<ASDF:SYSTEM "sb-posix"> 17592166825703 0) 24: (ASDF:LOAD-SYSTEM #<ASDF:SYSTEM "sb-posix">) 25: (ASDF::MODULE-PROVIDE-ASDF SB-POSIX) 26: ((LAMBDA (#:G[REQUIRE]13)) ASDF::MODULE-PROVIDE-ASDF) 27: (SB-IMPL::%MAP-FOR-EFFECT-ARITY-1 #<CLOSURE (LAMBDA #) {1003275809}> (ASDF::MODULE-PROVIDE-ASDF SB-IMPL::MODULE-PROVIDE-CONTRIB)) 28: (REQUIRE SB-POSIX NIL) 29: (SB-INT:SIMPLE-EVAL-IN-LEXENV (REQUIRE 'SB-POSIX) #<NULL-LEXENV>) 30: (SB-IMPL::PROCESS-EVAL/LOAD-OPTIONS ((:LOAD . "asdf.lisp") (:EVAL . "(require 'sb-posix)") (:EVAL . "(quit)"))) 31: (SB-IMPL::TOPLEVEL-INIT) 32: ((LABELS SB-IMPL::RESTART-LISP))
unhandled condition in --disable-debugger mode, quitting ; ; compilation unit aborted ; caught 1 fatal ERROR condition
The same thing works fine in ASDF 2.012. What should I do?
Also, I use the unexported MISSING-REQUIRES and MISSING-REQUIRED-BY to do autoloading of missing system components. Is there any chance they'll become an exported supported interface in the next version?
Zach
Faré <fahree@gmail.com> writes:
Ouch, I might have messed up with the SBCL_HOME treatment of 2.012.9. Do you get the same behavior in 2.012.8?
2.012.8 (commit 566a4234) has the style warnings but does not fail.
Can you tell me the values of the following
*source-registry* *output-translations* (getenv "SBCL_HOME")
NIL, NIL, "/usr/local/lib/sbcl". Zach
On 17 March 2011 00:22, Zach Beane <xach@xach.com> wrote:
Faré <fahree@gmail.com> writes:
Ouch, I might have messed up with the SBCL_HOME treatment of 2.012.9. Do you get the same behavior in 2.012.8?
2.012.8 (commit 566a4234) has the style warnings but does not fail.
Thanks! So indeed 2.012.9 is the culprit. I'll work on the style warnings, but I need more input to fix the other problem.
Can you tell me the values of the following
*source-registry* *output-translations* (getenv "SBCL_HOME")
NIL, NIL, "/usr/local/lib/sbcl".
Please give me the values of these after a (initialize-source-registry) and a (initialize-output-translations). And also give me (truename (getenv "SBCL_HOME")) and (truenamize (getenv "SBCL_HOME")) [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Be careful what you set your heart on — for it will surely be yours. — James Baldwin, "Nobody Knows My Name"
Faré <fahree@gmail.com> writes:
Please give me the values of these after a (initialize-source-registry) and a (initialize-output-translations). And also give me (truename (getenv "SBCL_HOME")) and (truenamize (getenv "SBCL_HOME"))
*source-registry* is: ((#P"/usr/local/lib/sbcl/" #P"/usr/local/lib/sbcl/asdf-install/" #P"/usr/local/lib/sbcl/asdf/" #P"/usr/local/lib/sbcl/sb-aclrepl/" #P"/usr/local/lib/sbcl/sb-bsd-sockets/" #P"/usr/local/lib/sbcl/sb-bsd-sockets/alien/" #P"/usr/local/lib/sbcl/sb-cltl2/" #P"/usr/local/lib/sbcl/sb-concurrency/" #P"/usr/local/lib/sbcl/sb-concurrency/tests/" #P"/usr/local/lib/sbcl/sb-cover/" #P"/usr/local/lib/sbcl/sb-cover/test-output/" #P"/usr/local/lib/sbcl/sb-executable/" #P"/usr/local/lib/sbcl/sb-grovel/" #P"/usr/local/lib/sbcl/sb-introspect/" #P"/usr/local/lib/sbcl/sb-md5/" #P"/usr/local/lib/sbcl/sb-posix/" #P"/usr/local/lib/sbcl/sb-posix/alien/" #P"/usr/local/lib/sbcl/sb-posix/test-lab/" #P"/usr/local/lib/sbcl/sb-posix/test-output/" #P"/usr/local/lib/sbcl/sb-queue/" #P"/usr/local/lib/sbcl/sb-rotate-byte/" #P"/usr/local/lib/sbcl/sb-rt/" #P"/usr/local/lib/sbcl/sb-simple-streams/" #P"/usr/local/lib/sbcl/sb-sprof/" #P"/usr/local/lib/sbcl/site-systems/" #P"/home/xach/.sbcl/systems/" #P"/home/xach/src/asdf/")) *output-translations* is: (((#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*" T) (#P"/usr/local/lib/sbcl/**/*.*" T) (#P"/usr/local/lib/sbcl/**/*.*" #P"/usr/local/lib/sbcl/**/*.*") (T #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*"))) (truename (getenv "SBCL_HOME")) is #P"/usr/local/lib/sbcl/". (truenamize (getenv "SBCL_HOME")) is #P"/usr/local/lib/sbcl/". Zach
Zach Beane <xach@xach.com> writes:
Faré <fahree@gmail.com> writes:
Please give me the values of these after a (initialize-source-registry) and a (initialize-output-translations). And also give me (truename (getenv "SBCL_HOME")) and (truenamize (getenv "SBCL_HOME"))
*source-registry* is: [snip]
Sorry, the previous email was for 2.012.8. The *source-registry* and SBCL_HOME values are the same, but the *output-translations* differ.
*output-translations* is:
(((#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*" T) (#P"/usr/local/lib/sbcl/**/*.*" T) (#P"/usr/local/lib/sbcl/**/*.*" #P"/usr/local/lib/sbcl/**/*.*") (T #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*")))
In 2.012.9 the *output-translations* are: (((#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*" T) (#P"/usr/local/lib/sbcl/*.*" T) (#P"/usr/local/lib/sbcl/" #P"/usr/local/lib/sbcl/") (T #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*"))) Zach
On 17 March 2011 13:44, Zach Beane <xach@xach.com> wrote:
*output-translations* is:
(((#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*" T) (#P"/usr/local/lib/sbcl/**/*.*" T) (#P"/usr/local/lib/sbcl/**/*.*" #P"/usr/local/lib/sbcl/**/*.*") (T #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*")))
In 2.012.9 the *output-translations* are:
(((#P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*" T) (#P"/usr/local/lib/sbcl/*.*" T) (#P"/usr/local/lib/sbcl/" #P"/usr/local/lib/sbcl/") (T #P"/home/xach/.cache/common-lisp/sbcl-1.0.46-linux-amd64/**/*.*")))
Aha. Found it. Sorry. Please try 2.012.10. PS: Nikodemus, in which error messages would you insert newlines? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices.
On 17 March 2011 21:38, Faré <fahree@gmail.com> wrote:
PS: Nikodemus, in which error messages would you insert newlines?
1. In all ones over ~70 characters long. Exact point doesn't seem that important, but less than 80 at any rate. 2. In ones that have potentially long ~A or ~S bits in them I'd do "Mumble mumble:~ ~% ~S~ ~%mumble some more." or similar. "Potentially long" includes all pathnames and pathname designators, lists, and all objects that may have user-defined PRINT-OBJECT methods -- or perhaps more practically, anything that may contain newlines or isn't virtually guaranteed to print as a dozen characters or less. Cheers, -- Nikodemus
* Nikodemus Siivola <avxbqrzhf-/J93COK4J+RAf9mLN2ZmLD@choyvp.tznar.bet> [2011-03-18 08:17:32 +0200]:
PS: Nikodemus, in which error messages would you insert newlines?
1. In all ones over ~70 characters long. Exact point doesn't seem that important, but less than 80 at any rate.
I think this is wrong. I think the underlying CL implementation should take care of the proper error message formatting, splitting the lines depending on the window size. -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.5 (Final) X http://jihadwatch.org http://dhimmi.com http://camera.org http://iris.org.il http://mideasttruth.com http://openvotingconsortium.org Old Age Comes at a Bad Time.
On 18 March 2011 16:58, Sam Steingold <sds@gnu.org> wrote:
1. In all ones over ~70 characters long. Exact point doesn't seem that important, but less than 80 at any rate.
I think this is wrong. I think the underlying CL implementation should take care of the proper error message formatting, splitting the lines depending on the window
I agree -- but ~@< directives which did that got removed for Genera compatibility. Cheers, -- Nikodemus
On 18 March 2011 19:44, Nikodemus Siivola <nikodemus@random-state.net> wrote:
On 18 March 2011 16:58, Sam Steingold <sds@gnu.org> wrote:
1. In all ones over ~70 characters long. Exact point doesn't seem that important, but less than 80 at any rate.
I think this is wrong. I think the underlying CL implementation should take care of the proper error message formatting, splitting the lines depending on the window
I agree -- but ~@< directives which did that got removed for Genera compatibility.
OK, should be all fixed in 2.012.11, through a ugly-named compatibility function errfmt. Note that I don't distinguish between ~@:> and ~:> as before 2.012.8 -- does that matter much? Please git show 2.012.8 -- asdf.lisp to tell me if that matters, in which case I'll have to be more subtle. Other minor issues fixed as well. Unless there are further requests or bugs found, I intend to release 2.012.11 as 2.013 this weekend, then ask all vendors to upgrade. Please test and review with your favorite implementation. PS: thanks a lot for all the feedback. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] It's better to know nothing that to know what ain't so. — Josh Billings
participants (4)
-
Faré -
Nikodemus Siivola -
Sam Steingold -
Zach Beane