ASDF MCL or OpenMCL bug?

Under OpenMCL I'm getting a bad path returned from component-pathname 
which merges the following:


component-parent-pathname - uffi:src;

component-relative-pathname - uffi:package.lisp


Under MCL the same code gives:


component-parent-pathname - uffi:src;

component-relative-pathname - package.lisp


The issue comes from make-pathname here:

(defmethod component-relative-pathname ((component source-file))
   (let ((*default-pathname-defaults* (component-parent-pathname component)))
     (or (slot-value component 'relative-pathname)
	(make-pathname :name (component-name component)
		       :type
		       (source-file-type component
					 (component-system component))))))


I had no problems with MCL, ACL, or LispWorks, but it seems that 
OpenMCL might be doing the correct thing according to the specs:

defaults---a pathname designator. The default is a pathname whose 
host component is the same as the host component of the value of 
*default-pathname-defaults*, and whose other components are all nil.


What needs to change? I added :host nil to the make-pathname in 
component-relative-pathname for now.

Thanks,

John DeSoi, Ph.D.



P.S. There are still a number of compiler warnings (asdf 1.37):

;Compiler warnings :
;   Unused lexical variable NEW-VALUE, in ((SETF VISITING-COMPONENT) 
(T T T)) inside an anonymous lambda form.
;   Unused lexical variable OPERATION, in ((SETF VISITING-COMPONENT) 
(T T T)) inside an anonymous lambda form.
;   Unused lexical variable COMPONENT, in ((SETF VISITING-COMPONENT) 
(T T T)) inside an anonymous lambda form.
;   Variable OUTPUT not ignored, in (PERFORM (COMPILE-OP 
CL-SOURCE-FILE)) inside an anonymous lambda form.


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390