[Armedbear-ticket] [armedbear] #365: ABCL-Jar not working on Mac OS X

[armedbear]

#365: ABCL-Jar not working on Mac OS X
-----------------------------+-----------------------
  Reporter:  robert goldman  |      Owner:  mevenson
      Type:  defect          |     Status:  reopened
  Priority:  major           |  Milestone:  1.4.0
 Component:  abcl-contrib    |    Version:  1.4.0-dev
Resolution:                  |   Keywords:
-----------------------------+-----------------------
Changes (by robert goldman):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I have just updated from SVN and rebuilt, and the asdf-jar packaging still
 fails for me, although it fails with a different error now.
 Here's what I see in the slime repl:
 {{{
 luation aborted on #<FILE-ERROR {2B53822}>.
 CL-USER> (asdf-jar:package "abcl-prism" :recursive nil)

 Packaging ASDF definition of #<ASDF/SYSTEM:SYSTEM "abcl-prism">
 Packaging contents in /var/tmp/abcl-prism.jar
 }}}
 And here's the debugger window contents:
 {{{
 Unsupported directory component "abcl-prism".
    [Condition of type FILE-ERROR]

 Restarts:
  0: [RETRY] Retry SLIME REPL evaluation request.
  1: [*ABORT] Return to SLIME's top level.
  2: [ABORT] Abort thread.

 Backtrace:
   0: (#<FUNCTION {2D5FD903}> #<FILE-ERROR {331A2257}> #<FUNCTION
 {2D5FD903}>)
   1: (APPLY #<FUNCTION {2D5FD903}> (#<FILE-ERROR {331A2257}> #<FUNCTION
 {2D5FD903}>))
   2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<FILE-ERROR
 {331A2257}> #<FUNCTION {2D5FD903}>)
   3: (INVOKE-DEBUGGER #<FILE-ERROR {331A2257}>)
   4: org.armedbear.lisp.Lisp.error(Lisp.java:382)
   5: org.armedbear.lisp.Pathname.getDirectoryNamestring(Pathname.java:808)
   6: org.armedbear.lisp.Pathname.getNamestring(Pathname.java:700)
   7: org.armedbear.lisp.zip.execute(zip.java:220)
   8: org.armedbear.lisp.zip.execute(zip.java:68)
   9: org.armedbear.lisp.Symbol.execute(Symbol.java:814)
  10: org.armedbear.lisp.LispThread.execute(LispThread.java:832)
  11: org.armedbear.lisp.asdf_jar_TMP_1.execute(asdf-jar.lisp:15)
  12: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:121)
  13: org.armedbear.lisp.LispThread.execute(LispThread.java:851)
  14: org.armedbear.lisp.Lisp.evalCall(Lisp.java:589)
  15: org.armedbear.lisp.Lisp.eval(Lisp.java:540)
  16: org.armedbear.lisp.Primitives$pf__eval.execute(Primitives.java:345)
  17: (SYSTEM:ZIP #P"/var/tmp/abcl-prism.jar" #<EQUAL HASH-TABLE 7 entries,
 11 buckets {78C497F6}>)
  18: (PACKAGE "abcl-prism" :RECURSIVE NIL)
  19: (SYSTEM::%EVAL (PACKAGE "abcl-prism" :RECURSIVE NIL))
  --more--
 }}}
 The hashtable contents are as follows:
 {{{
 #<HASH-TABLE {78C497F6}>
 --------------------
 Count: 7
 Size: 11
 Test: EQUAL
 Rehash size: 1.5
 Rehash threshold: 0.75
 [clear hashtable]
 Contents:
 #P"/Users/rpg/prismatic/code/quiksilver/abcl/abcl-prism.asd" = #P"abcl-
 prism/abcl-prism.asd" [remove entry]
 #P"/Users/rpg/.cache/common-lisp/abcl-1.4.0-dev-
 fasl42-macosx-x64/Users/rpg/prismatic/code/quiksilver/abcl/package.abcl" =
 #<PATHNAME <<error printing object>> {33A72123}> [remove entry]
 #P"/Users/rpg/.cache/common-lisp/abcl-1.4.0-dev-
 fasl42-macosx-x64/Users/rpg/prismatic/code/quiksilver/abcl/utils.abcl" =
 #<PATHNAME <<error printing object>> {21709B53}> [remove entry]
 #P"/Users/rpg/prismatic/code/quiksilver/abcl/package.lisp" = #P"abcl-
 prism/package.lisp" [remove entry]
 #P"/Users/rpg/prismatic/code/quiksilver/abcl/utils.lisp" = #P"abcl-
 prism/utils.lisp" [remove entry]
 #P"/Users/rpg/prismatic/code/quiksilver/abcl/add-script.lisp" = #P"abcl-
 prism/add-script.lisp" [remove entry]
 #P"/Users/rpg/.cache/common-lisp/abcl-1.4.0-dev-
 fasl42-macosx-x64/Users/rpg/prismatic/code/quiksilver/abcl/add-
 script.abcl" = #<PATHNAME <<error printing object>> {67E5774B}> [remove
 entry]
 }}}

 I note that the mapped pathnames for all of the compiled files gives an
 error on printing, although the source files are all ok.

 Unfortunately, when I attempt to do anything with the bad pathnames, even
 `describe`, it causes a crash in some print method.  However, I have
 determined that the `pathname-directory` returned from one of these is
 `"abcl-prism"`, and the `pathname-directory` of a working pathname is
 `(:relative "abcl-prism")`, so I believe there's still a mapping bug.

--
Ticket URL: <http://abcl.org/trac/ticket/365#comment:8>
armedbear <http://abcl.org>
armedbear