If Hamlib configure finds libgd, it will configure itself to build
supplemental documentation that is ultimately never built or installed.
Explicitly disable for improved build consistency.
Configure option --with-rpc-backends was removed in v3.0 (2015).
Configure option --with-cxx-binding is on by default.
Make Tcl and Python tests work.
Move examples into examples dir and make them easily runnable.
ok sthen@
Add missing header and move variable so that they're usable from the
x86-only fallback code. This undoes part of
https://github.com/Hamlib/Hamlib/commit/d20a2358606bec98e232be0a7dbbfacafe98b2ab
Tweak #ifdef check to use the default code path on Unix/Linux. We don't
implement all the features specified by _POSIX_TIMERS, but we do
implement clock_gettime(CLOCK_MONOTONIC) as required by POSIX 2008.
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
since SHARED_ONLY support was removed across the ports tree the perl module
no longer adds it, so it must be done manually for any perl ports that
provide perl shared-library modules (i.e. libdata/perl5/site_perl/$ARCH/*.so)
and you must not remove them from WANTLIB even if they show as "Extra".
couple of fallouts. Note that these ports are only the ones that used to
have a direct dependency on devel/libusb so there may be some other
hidden ports that may break because of the switch. If that's the case,
no need to start ranting all over but instead tell me which one(s)
break. Thanks.
Note: sysutils/nut hasn't been fixed yet but will be today.
stu