On Sat, Nov 02 2019, Kurt Mosiejczuk <k...@cranky.work> wrote: > So the existing py-numpy is unhappy with the 2.7 update and it seems to > be clashes between clang and gcc. > > This is the last version of py-numpy to work with Python 2.7. 1.17.x will > be Python 3.5+ only.
To stay on the safe side, here's a simple diff for lang/python/2.7 which unbreaks numpy and maybe others. clang doesn't error out, gcc does. Why does numpy use gcc? Index: Makefile =================================================================== RCS file: /cvs/ports/lang/python/2.7/Makefile,v retrieving revision 1.63 diff -u -p -r1.63 Makefile --- Makefile 1 Nov 2019 17:40:08 -0000 1.63 +++ Makefile 2 Nov 2019 21:13:16 -0000 @@ -11,6 +11,7 @@ SHARED_LIBS = python2.7 0.0 VERSION_SPEC = >=2.7,<2.8 CONFIGURE_ARGS += --with-ensurepip=no +CONFIGURE_ENV += ac_cv_opt_olimit_ok=no PORTROACH = limit:^2\.7 -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
