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.
The only change is in 3rdparty/lua-zlib/lua_zlib.c:
- SETLITERAL("_VERSION", "lua-zlib $Id$ (tag: mame0222, release0222)");
+ SETLITERAL("_VERSION", "lua-zlib $Id$ (tag: mame0222)");
Pointed out by naddy@, thanks!
The affected *.make files are produced by the genie build tool.
The genie bootstrap build uses pre-generated sources and does not
pick up the patched file. We add a pre-build target that first
builds genie, then runs genie to regenerate the source files. The
main build will then create a fixed genie.
ok fcambus@
no need to consider the case with a ports-clang compiler on a gcc arch (which
uses libstdc++ not libc++). amd64 test and ok jca
(i386 is broken due to a different issue)
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.
ELF_RANDOMIZE_LIMIT was bumped to 1MB for retguard, but MAME actually
requires 4MB, so it fails on statup.
There is no sense bumping ELF_RANDOMIZE_LIMIT again just for one program,
so disable retguard by adding -fno-ret-protector to CFLAGS.
Discussed with mortimer@
"localpng.h" substitutions. Some substitutions where not done, which
caused the build to fail when graphics/png is not installed.
OK nigel@, who initially reported the issue.
