Binary Compilation with defsystems having the same suffix

Describe the problem here. base.asd

(asdf:defsystem base
  :version "0"
  :description "BASE"
  :class asdf/bundle:program-system
  :build-operation asdf/bundle:program-op
  :build-pathname "base"
  :licence "Copyright"
  :depends-on (iolib/base cl-unicode)
  :serial t
  ;; components likely need manual reordering
  )

ecl -load ~/.quicklisp/setup.lisp -load base.asd
(asdf:make :base)

Condition of type: SIMPLE-ERROR
Error code 1 when executing
(RUN-PROGRAM "gcc" ...)

Binary not created

Provide details regarding ECL version (or preferably commit), operating system and if revelant the build options and versions of the build tools.

(lisp-implementation-version) "16.1.3"
(ext:lisp-implementation-vcs-id)` "470ad979be2ba25af2631e163846ddaed528ce2b"
(software-type) "Linux"
(software-version) "4.8.0-34-generic"
(machine-type)"x86_64"
*features* (:QUICKLISP :ASDF-PACKAGE-SYSTEM :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX
 :NON-BASE-CHARS-EXIST-P :ASDF-UNICODE :WALKER :CDR-1 :CDR-5 :LINUX :FORMATTER
 :CDR-7 :ECL-WEAK-HASH :LITTLE-ENDIAN :ECL-READ-WRITE-LOCK :LONG-LONG :UINT64-T
 :UINT32-T :UINT16-T :RELATIVE-PACKAGE-NAMES :LONG-FLOAT :UNICODE :DFFI
 :CLOS-STREAMS :CMU-FORMAT :UNIX :ECL-PDE :DLOPEN :CLOS :THREADS :BOEHM-GC
 :ANSI-CL :COMMON-LISP :IEEE-FLOATING-POINT :CDR-14 :PREFIXED-API :FFI :X86_64
 :COMMON :ECL)

Some additional notes.

could you paste full error of the compiler?

/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/cl-unicode-0.1.5/cl-unicode/base.a(eclinitwWNtx4.o): In function `init_lib_BASE':
/tmp/eclinitwWNtx4.c:77: multiple definition of `init_lib_BASE'
/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/iolib-v0.8.1/src/base/iolib/base.a(eclinitCqrXAB.o):/tmp/eclinitCqrXAB.c:137: first defined here
collect2: error: ld returned 1 exit status

Condition of type: SIMPLE-ERROR
Error code 1 when executing
(RUN-PROGRAM "gcc" ("-o" "base" "-L/usr/local/lib/" "/tmp/eclinitXiKdml.o" "/usr/local/lib/ecl-16.1.3/libcmp.a" "/usr/local/lib/ecl-16.1.3/libasdf.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/alexandria-20161031-git/alexandria.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/iolib-v0.8.1/src/new-cl/iolib/common-lisp.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/split-sequence-1.2/split-sequence.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/iolib-v0.8.1/src/base/iolib/base.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/cl-ppcre-2.0.11/cl-ppcre.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/cl-unicode-0.1.5/cl-unicode/base.a" "/home/coder/.cache/common-lisp/ecl-16.1.3-470ad979-linux-x64/home/coder/.quicklisp/dists/quicklisp/software/cl-unicode-0.1.5/cl-unicode.a" "-Wl,--rpath,/usr/local/lib/" "-lecl" "-lgmp" ...))
Available restarts:

1. (CONTINUE) Continues anyway.
2. (RETRY) Retry PROGRAM-OP on #<program-system "base">.
3. (ACCEPT) Continue, treating PROGRAM-OP on #<program-system "base"> as having been successful.
4. (RETRY) Retry ASDF operation.
5. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration.
6. (RESTART-TOPLEVEL) Go back to Top-Level REPL.

Broken at SI:BYTECODES. [Evaluation of: (ASDF/OPERATE:MAKE :BASE)] In: #<process TOP-LEVEL>.

OK, this is an actual bug in ECL – thanks! I don't have good solution for it yet.

steps to reproduce (note wrapper):

(c::compute-init-name "danny/base" :kind :static-library :wrapper t)
(c::compute-init-name "jenny/base" :kind :static-library :wrapper t)

changed milestone to %ECL 16.2.0

first argument should be a pathname, so it's actually asdf bug, but we have to make a workaround for that because asdf won't probably shy away from using pathname-like system names.