The LLVM Project is a collection of modular and reusable compiler and
toolchain technologies.
This port includes Clang (a C/C++/Objective-C compiler), LLD (a linker),
LLDB (a debugger), an OpenMP runtime library, and the LLVM infrastructure
these are built on.
WWW: http://llvm.org/
===> The following configuration options are available for llvm50-5.0.2_3:
CLANG=on: Build clang
COMPILER_RT=on: Sanitizer libraries
DOCS=on: Build and/or install documentation
EXTRAS=on: Extra clang tools
GOLD=on: Build the LLVM Gold plugin for LTO
LIT=on: Install lit and FileCheck test tools
LLD=on: Install lld, the LLVM linker
LLDB=on: Install lldb, the LLVM debugger
OPENMP=on: Install libomp, the LLVM OpenMP runtime library
===> Use 'make config' to modify these settings
Don't override the compiler on armv7.
The base system compiler is now sufficent to build and link.
No version bump. While technically required for armv7, forcing everyone
to rebuild for this minor change that doesn't effect actual use is not
justifiable.
PR: 235282
Submitted by: jbeich
More throughly disable assertions. This works around USES=cmake
overriding the CFLAGS used to build. [0]
devel/llvm[45]0: Fix build on GCC systems. [1]
devel/llvm[456]: Avoid realpath calls where possible in the wrapper
script. [2]
PR: 233506 [0], 234647 [1], 234937 [1]
Submitted by: greg@unrelenting.technology [0], pkubaj@anongoth.pl [1],
bdrewery [2]
Differential Revision: https://reviews.freebsd.org/D17990
Change cmake default behaviour to outsource.
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC
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
Use exec in wrapper to avoid an extra shell process sticking around.
I purposely didn't bump PORTREVISION for this as it's not really
worth a rebuild even though technically required.
Approved by: brooks
Remove compatibility code for FreeBSD < 11.2 from all ports.
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
Limit LLVM builds to linking a single binary at a time.
Regular builds can requires multiple gigabytes of memory at Debug builds
can exceed 100GB. This should help low-memory systems such as
Raspberry-Pis and VMs.
Submitted by: dim
Bump PORTREVISION for ports depending on the canonical version of GCC
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
devel/llvm*: Fix wrapper scripts to support symlinking to them
The wrapper scripts currently do not resolve the real path to $0:
$ install -l rs /usr/local/bin/clang50 gcc
$ ./gcc
./gcc: /usr/local/llvm50/bin/gcc: not found
Here /usr/local/llvm50/bin/clang should be called not
/usr/local/llvm50/bin/gcc.
Approved by: brooks (maintainer)
Differential Revision: https://reviews.freebsd.org/D14727
Upgrade to 5.0.1.
Add a local distfile backup while LLVM sorts out mirror issues.
Correct shared linkage with llvm-config50.[0]
PR: 223191 [0]
Submitted by: greg@unrelenting.technology [0]
MFH: 2018Q1
Merge from src:
lld: accept EINVAL to indicate posix_fallocate is unsupported
As of r325320 posix_fallocate on a ZFS filesystem returns EINVAL to
indicate that the operation is not supported. (I think this is a strange
choice of errno on the part of POSIX.)
PR: 223383, 223440
Reported by: Mark Millard
- add support for ARMv7
- for ARMv[67], use correct API when building CONFIGURE_TARGET
PR: 219779
Submitted by: Sylvain Garrigues <sylvain@sylvaingarrigues.com>
Disable LLDB builds on 10.x as they don't link.
Attempt to correct default targets. [0]
Fix more references to clang-format50 and use a more future proof
patching approach. [1]
Build and install pp-trace with the EXTRAS target.
PR: 219779 [0], 220995 [1], 222380 [2]