On 2019 May 27 (Mon) at 20:57:55 +0200 (+0200), Martin Reindl wrote:
:Digging deeper here. This is my interpretation, please correct me if I
:am wrong:
:
:On aarch64, the current COMPILER line expands to:
:- base-clang: no fortran suport, no compiler link is set up
:- ports-gcc: aarch64 is not in GCC49_ARCHS, no compiler link is set up
:(gcc4.9 had no fortran for aarch64 anyway)
:- base-gcc: does not match on clang arch
:
:math/R works around this by using flang, but ports-gcc has moved from
:4.9 to 8 now and gained fortran support for aarch64. So really,
:ports/infrastructure/mk should also transition from GCC49 to GCC8.
:
:Here is a quick hack to see if I am moving in the right direction (at
:least this makes py-scipy on aarch64 work without the above diff).
:
:Opinions?
:
:Index: arch-defines.mk
:===================================================================
:RCS file: /cvs/ports/infrastructure/mk/arch-defines.mk,v
:retrieving revision 1.64
:diff -u -p -r1.64 arch-defines.mk
:--- arch-defines.mk 11 May 2019 12:05:46 -0000 1.64
:+++ arch-defines.mk 27 May 2019 18:52:04 -0000
:@@ -36,7 +36,7 @@ LLD_ARCHS = aarch64 amd64 arm i386
: # as well as available for PROPERTIES checks.
: LLVM_ARCHS = aarch64 amd64 arm i386 mips64 mips64el powerpc sparc64
: # arches where gcc4.9 exists. To be used again for modules
:-GCC49_ARCHS =alpha amd64 arm hppa i386 mips64 mips64el powerpc sparc64
:+GCC49_ARCHS = aarch64 alpha amd64 arm hppa i386 mips64 mips64el powerpc
:sparc64
:
: # arches where there is a C++11 compiler, either clang in base or gcc4
: CXX11_ARCHS = ${CLANG_ARCHS} ${GCC49_ARCHS}
:
I slipped the above into a bulk build, but iirc I was doing this before
when testing gcc-8.
OK, with renaming GCC49_ARCHES to something slightly more accurate as a
later step.
--
The new Congressmen say they're going to turn the government around. I
hope I don't get run over again.
