Those are already in TARGET_CONFIGURE_ARGS. Also get rid of unused
BR2_AC_CV_FUNC_MALLOC_0_NONNULL variable.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Not particular useful until we add dbus-python (which depends on a fixed up
dbus-glib, which in turn depends on us starting to compile glib/dbus/dbus-glib
for the host as well) - But that's for another day.
The avahi-autoipd target install step adds /var/lib/avahi-autoipd as a
symlink to /tmp/avahi-autoipd, which is fine, except if your /var/lib is
already a symlink to /tmp (E.G. like the default target_skeleton is).
If that's the case, then you end up adding a /tmp/avahi-autoipd symlink
pointing to itself, causing subsequent builds to fail
(Too many levels of symbolic links in the ln -sf call). Fix it by simply
first removing the symlink if it's there.
Avahi uses autoconf during ./configure, make sure it is available and used
before building avahi.
Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
This patch puts gettext and libintl before the avahi targets, thus making sure
they exist before avahi targets are built.
Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
Depend on dbus-daemon in staging_dir instead of in target_dir as
fakeroot updates the timestamp on the target_dir version every time,
so the avahi makefile thinks it always needs to recompile avahi.
they should be configured with --prefix=/usr and we then need to use
make DESTDIR=$(STAGING_DIR) install to get things installed into the
staging directory. The current situation for many packages, which use
--prefix=$(STAGING_DIR) results in the staging_dir paths getting compiled
into the binary itself.
This also adds in a pile of libtool fixups. Between broken pkgconfig,
broken libtool handling, and broken --prefix settings, its a wonder
things have worked as well as they have up till now.
-Erik
