On CONFIG builds, er_card_slot is not used,
but is defined. This is an error for us.

We were destroying something that could be
uninitialized. The solution was to invert
and correct the order of destruction of
objects.

This was effectively skipping compilation of
AFC Diagnostics module.

With this we have more control over a faulty
child DEVIO, for instance.

This was based on the functions available on
dev_mngr (src/dev_mngr/dev_mngr_core.c and
include/dev_io_core.h)

In fact, we need this for non AFC boards,
like ml605 which does not have AFC DIAG modules.
Thus, no addresses for AFC DIAG module exists in the
mem_layout.h file, causing the compilation to fail.

This reverts commit 05d338d3.

The conditional compilation was used before
the linker table. Now this is not necessary
and, in fact, is an error as afcv3_1 sttills needs
this module, but would not be compile with it as
just afcv3 is specified in the Makefile.

In fact, specifyng it is an error as upstart
will hang on start/stop

As all of the Malamute is a draft API, we need
this for Malamute version 1.0.0

As all of the Malamute is a draft API, we need
this for Malamute version 1.0.0

As all of the Malamute is a draft API, we need
this

This is a stable upstream version. So, we
prefer that this one instead of the old 0.1.0.

Malamute current version 1.0.0 changed the
MACRO version to MLM_VERSION. So, we update it
here.

The only difference from AFCv3 is the
EEPROM address, which is correct (0x50 and 0x52
for the FMC1 and FMC2 slots, respectively) in this
version.

As we can have multiple application, we don't
need to check if APPS is set to a specific
value. If anything goes wrong, the Makefile will
fail accordingly.

With this we could build multiple apps
simultaneously, with a single make, like:

make APPS='"ebpm pbpm"' <other options> or
sudo ./compile.sh '"ebpm pbpm"' <other options>

We don't have a Install section.
So, no need to install it.