Something in protobuf system breaks the ASDF output file locations

[rpgoldman]

Normally, ASDF writes my compiled files into ~/.cache/common-lisp/. This lets me work with multiple CL implementations, since the FASL files for different implementations are in different directories.

Somehow, protobuf is breaking this for me. Is this intentional, or did it accidentally happen somehow as a side-effect of handling the protocol buffer operations? Or could this be something that happens because of com.google.base?

Here's an example; see the starred line where it goes awry:

; Fast loading
;    /Users/rpg/.cache/common-lisp/acl-10.0-macosx-x64/Users/rpg/quicklisp/dists/quicklisp/software/nibbles-20150709-git/sbcl-opt/x86-vm.fasl
;;; Compiling file
;;;   /Users/rpg/quicklisp/dists/quicklisp/software/nibbles-20150709-git/sbcl-opt/x86-64-vm.lisp
;;; Writing fasl file
;;;   /Users/rpg/.cache/common-lisp/acl-10.0-macosx-x64/Users/rpg/quicklisp/dists/quicklisp/software/nibbles-20150709-git/sbcl-opt/x86-64-vm-tmpe6to2q24.fasl
;;; Fasl write complete
; Fast loading
;    /Users/rpg/.cache/common-lisp/acl-10.0-macosx-x64/Users/rpg/quicklisp/dists/quicklisp/software/nibbles-20150709-git/sbcl-opt/x86-64-vm.fasl
;;; ************* Here's where things change.
;;; Compiling file
;;;   home:projects;gridguard;protobuf-cl;varint;package.lisp
;;;   (/Users/rpg/projects/gridguard/protobuf-cl/varint/package.lisp)
;;; Writing fasl file
;;;   /Users/rpg/projects/gridguard/protobuf-cl/varint/package-tmpyyle3wr2.fasl
;;; Fasl write complete
; Fast loading home:projects;gridguard;protobuf-cl;varint;package.fasl
;    (/Users/rpg/projects/gridguard/protobuf-cl/varint/package.fasl)
Warning: unable to safely change compiler optimization policy
;;; Compiling file
;;;   home:projects;gridguard;protobuf-cl;varint;varint.lisp
;;;   (/Users/rpg/projects/gridguard/protobuf-cl/varint/varint.lisp)

[rpgoldman]

Not a real issue -- it was the use of logical pathnames that broke things. Ugh, they suck.

Sorry for the false alarm.