on clang arches this is a noop, on !clang arches this gives a path to
the estdc++ WANTLIB. needed because this is a multi-package port and
LIB_DEPENDS-main doesn't include the default LIB_DEPENDS added by
gcc4.port.mk.
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.
surprising.
It's always controlled by MODPY_BUILDDEP, which defaults to Yes
usually, unless NO_BUILD=Yes is set, and then it defaults to No.
this caters to matthieu's xcbgen port
okay aja@, rpointel@
BIO_up_ref, X509_STORE_get0_objects but not X509_NAME_ENTRY_set,
SSL_CTX_get_default_passwd_cb, X509_OBJECT_get_type,
SSL_CTX_get_default_passwd_cb_userdata, X509_STORE_get0_param,
SSL_SESSION_has_ticket, SSL_SESSION_get_ticket_lifetime_hint
while there: don't override TLS_*method with macros
This will allow us to drop patches and substitutions in our ports tree. Nowadays
most upstreams don't hardcode the path to python but instead use env(1) to find
the path.
bulk tested
ok sthen@
ok and input from rpointel@ (on an older patch)
- we don't have xlocale
- so we use __bsd_locale_fallbacks_h, yes even for #include <iostream>
- that depends on mbsnrtowcs and wcsnrtombs from wchar.h
- those require __POSIX_VISIBLE to be >= 200809...
bump accordingly. tested by naddy@, no breakage on gcc platforms.
with native c++ code worked fine. We no longer need to do that, and
llvm errors out with the non-sensical combination of "c++ -std=c99".
this fixes the python build on arm64
tested by sthen@ in an i386 bulk, thanks!
OK sthen@, rpointel@ (maintainer)
fixes by shadchin@, bulk build by me, support from danj@, no objection
from naddy@
All 250-something ports depending on python3 will be bumped in a few.
Fasten your seatbelts.
Beginning with Python 3.5 .pyo files are no longer used and
have been replaced by a more flexible scheme that includes
the optimization level explicitly in .pyc name (See PEP-488).
