This reverts 5b5659850d.
In hindsight I have to admit I did not correctly understand the
implications of the uclibc++.mk include.
The include allows a package to follow the user's choice regarding which
C++ library should be the standard. Linking against uClibc++ instead of
libstd++ is not a problem when running musl (which is what I had
incorrectly assumed), as both C++ libs are separate packages. And
uClibc++ is a lot smaller than libstd++, which is probably why it is
even the default C++ lib on OpenWrt currently.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Make sure that the c++ headers get installed to the staging directory
when libtiffxx was selected/built.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
tiff already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the tiff build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Also with $(FPIC) in CFLAGS even the tiff utils get compiled with PIC,
which us undesirable.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The include injects a lib depend on libuClibc++.so.0 into the package,
even on musl. Remove it and replace the depend with libstcpp instead.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The libtiff library declares an `ftell()` compat macro redirecting calls
to `ftello()` if such an implementation exists. The compat macro however
is declared with a wrong number of arguments, leading to the following
error on our buildbots:
In file included from .../usr/include/uClibc++/iostream:29:0,
from tif_stream.cxx:31:
.../usr/include/uClibc++/fstream:422:22: error: macro "ftell" requires 3 arguments, but only 1 given
retval = ftell(fp);
Add a patch to fix the macro definition in order to fix compilation of
the tiff package.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Sebastian Kemper