Based on further discussions with Duane Rettig and Kevin Layer at Franz.

Previous attempt to fix #141 had accidentally broken ASDF on Allegro versions prior to 11.

Necessary to build cleanly on Allegro v 11 (available now in beta).

Add new code for printing backtrace on clasp.  Previously, UIOP
treated clasp as if it was ECL.  Now we invoke
`clasp-debug:print-backtrace`, instead.

An inner read-time conditional #+(or clasp ecl mkcl) contained in an
outer, identical conditional has no effect.

These changes add support for the Mezzano operating system and its
Common Lisp implementation. They are based on changes originally
developed by Henry Harrington against ASDF 3.1.7.

At least versions of lispworks fail on DEFTYPE nested in EVAL-WHEN
:COMPILE-TOPLEVEL. This removes that on Lispworks.

It is wrong to call this function. If :init-name is not supplied, or
NIL ECL will compute the init name itself (it is not a new
mechanism).

Enabling specifying init-name makes it possible to build static and
shared libraries with known initialization function (important, when
CL module is linked with bigger C/C++ project outside ASDF).

If :init-name is NIL, it will default to compute-init-name
internally. Calling explicitly is not guaranteed to work in the
future (internal mechanism).

Fixes bundle builds for MKCL post 1.1.10.

Make sure to use c::build-program and not just c:build-program because
the symbol won't be external when using the ecl bytecode interpreter.

Elias Pipping authored Sep 21, 2016 and Robert Goldman committed Oct 05, 2016

In particular:
 - clasp does not define :ecl
 - use :os-unix instead of :unix
 - use :os-windows instead of :mswindows or :windows
 - use :os-macosx instead of :darwin
 - use :lispworks7+ instead of :lispworks7

Previous method was over-complicated.  Now we simply appropriately
define the type UIOP:FATAL-CONDITION, and we can do without both
UIOP:*FATAL-CONDITIONS* and UIOP::*FATAL-CONDITION-EXCEPTIONS*.

See https://bugs.launchpad.net/asdf/+bug/1605650

According to the spec, SERIOUS-CONDITIONs are "All conditions serious
enough to require interactive intervention if not handled should inherit
from the type serious-condition."  This is almost exactly the definition
of *FATAL-CONDITIONS*, so I substituted SERIOUS-CONDITION for ERROR
here.

Added exceptions to the set of *FATAL-CONDITIONS* in order to fix test
condition handling for CCL.  The exceptions permit us to have a class of
conditions (e.g., SERIOUS-CONDITION) that has a subclass that is not a
FATAL-CONDITION, but that does not have an obvious more specific
alternative.

The specific example that caused me to add this: On shutdown, CCL
signals CCL:PROCESS-RESET, a subclass of SERIOUS-CONDITION. So recent
test harness modifications to handle SERIOUS-CONDITIONs caused the test
scripts to mistakenly think there were failures because of calls to
EXIT-LISP.

A few are kept, for backward-compatibility with systems in quicklisp.

It's been the official way of calling CMUCL since 2011.

Avoid deprecation warning failing clean build.

Based on a contribution by Christian Shafmeister.

argument application-type was using the wrong feature keyword.

Fix test-program.script on allegro.

asdf/footer: non-functional tweak.
TODO: GCL bugs, original-initargs clients.