On powerpc64 OpenMP is always used when USE_THREADS is defined (which we do unconditionally). This means that OPENMP option on powerpc64 doesn't have any effect and it should be removed.
Clang also has some problems when linking Fortran libraries with OpenMP, so use GCC for powerpc64.
PR: 240379
Approved by: phd_kimberlite@yahoo.co.jp (maintainer), linimon (mentor)
This patch fixes build for PPC970 target. Since most people that run FreeBSD on powerpc64 use PowerPC 970 CPU's, switch to it by default and add non-default option to optimize for POWER6 (optimizing for newer POWER doesn't work on BE).
Bump PORTREVISION because of package change.
PR: 238868
Approved by: phd_kimberlite@yahoo.co.jp (maintainer), linimon (mentor)
Differential Revision: https://reviews.freebsd.org/D21010
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Previously I added these options only to the openmp build which isn't a default.
This change is requested by the upstream.
Ref. https://github.com/xianyi/OpenBLAS/issues/1882
Approved by: portmgr (unbreak)
NUM_THREADS= sets the build-time limit on the number of threads that apps can use with OpenBlas.
This unbreaks at least science/erkale's tests, and possibly some other software.
The upstream acknowledges the problem, recommended this solution for the port,
and are working on the permanent solution: https://github.com/xianyi/OpenBLAS/issues/1882
Approved by: portmgr blanket (unbreak)
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
* Fixed several thread race and locking bugs
* Fixed default LAPACK optimization level
* Updated LAPACK to 3.7.0
* Power
- Optimizations for Power9
- Fixed several Power8 assembly bugs
* ARM
- New optimized Vulcan and ThunderX2T99 targets
- Support for ARMV7 SOFT_FP ABI (make ARM_SOFTFP_ABI=1)
- Detect all cpu cores including offline ones
- Fix compilation with CLANG
* MIPS
- Fixed several threading issues
- Fix compilation with CLANG
* x86_64
- Detect Intel Bay Trail and Apollo Lake
- Detect Intel Sky Lake and Kaby Lake
- Detect Intel Knights Landing
- Detect AMD A8, A10, A12 and Ryzen
- Fix cmake builds for Haswell and related cpus
- Fix building for Sandybridge with CLANG 3.9
Pet portlint (USES vs. USE)
PR: 221633
Submitted by: truckman
Approved by: phd_kimberlite@yahoo.co.jp (maintainer)
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
The build still fails on 11 armv6, however MFC of r313873 will hopefully
fix the build there as well.
While here also add LICENSE_FILE and fix portlint warnings.
PR: 217279
Submitted by: mikael.urankar@gmail.com
Approved by: phd_kimberlite@yahoo.co.jp (maintainer), swills (mentor, implicit)
Differential Revision: https://reviews.freebsd.org/D9801
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms), part II.
The first part covered ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
This adds ports with USES=fortran and ports using Mk/bsd.octave.mk
which in turn has USES=fortran.
PR: 214965
Reported by: thierry
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
0.2.15 was released in October 2015.
Release notes: http://www.openblas.net/Changelog.txt
This update introduces support for new CPU architectures, such as Intel's
Broadwell and Skylake. In practice, this means people using those architectures
can actually build the port now (OpenBLAS seems to do some CPU-detection that
cannot be easily turned off and refusing to build on unrecognized CPUs).
Port changes:
- Reorganize a few variables in Makefile.
- Refresh patches.
PR: 206886
Submitted by: Adriaan de Groot <groot@kde.org> (first version),
Eijiro Shibusawa <phd_kimberlite@yahoo.co.jp> (maintainer)
MFH: 2016Q1
When using GH_TAGNAME the DISTNAME would have GH_PROJECT and GH_ACCOUNT in
it. When not using GH_TAGNAME it would not have this. Now both cases
will add in the GH_PROJECT and GH_ACCOUNT.
Add special care to ensure that the DISTVERSION is not added in twice. If
a port does GH_TAGNAME=v${PORTVERSION} it will be added in twice though. For
that case DISTVERSIONPREFIX=v should be set and no GH_TAGNAME should be used.
empty() is used rather than (!defined || !${}) to support fmake.
The purpose of setting DISTNAME at all in these cases is to make it more clear
that the distfile is from *GITHUB* and to avoid collisions if a project were
to be renamed or moved. Without adding in GH_PROJECT and GH_ACCOUNT then there
are real risks that collisions on filenames would happen on renamed or moved
projects, which is fairly common. A GITHUB-generated file may not match
a custom-rolled or git-archive-rolled distfile.
PR: 199069
With hat: portmgr
Testing done: All USE_GITHUB ports without GH_COMMIT were checksum/fetch/extract/WRKSRC tested.
(and replaced usage of _GCC_RUNTIME) by LDFLAGS which is a cleaner and
more robust approach.
PR: 197385
Submitted by: phd_kimberlite@yahoo.co.jp (maintainer)
and/or tabs before the =. This made doing regular expressions
on the ports tree really difficult.
Approved by: portmgr (not really, but touches unstaged ports)
GCC 4.6.4 to GCC 4.7.3. This entails updating the lang/gcc port as
well as changing the default in Mk/bsd.default-versions.mk.
Part II, Bump PORTREVISIONs.
PR: 182136
Supported by: Christoph Moench-Tegeder <cmt@burggraben.net> (fixing many ports)
Tested by: bdrewery (two -exp runs)
