| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we have a devel/llvm50 port, let's switch the CloudABI
toolchain port from LLVM 4.0 to 5.0. In addition to providing more
complete C++17 support, this will allow us to experiment with
C++ coroutines.
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D12401
Notes:
svn path=/head/; revision=450083
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As of FreeBSD 11, the cloudabi-toolchain port uses the ELF-toolchain
utilities for all the stuff not provided by LLVM. For FreeBSD 10 and
lower, we still rely on Binutils.
As CloudABI itself is only supported as of FreeBSD 11, there is hardly
any interest in supporting a Binutils based toolchain. Let's kick out
the CloudABI Binutils ports and symlink to the utilities in the base
system unconditionally.
Reviewed by: rene
Differential Revision: https://reviews.freebsd.org/D11733
Notes:
svn path=/head/; revision=446997
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CloudABI recently gained separate packages for ARMv7 based systems.
These systems can freely use ARMv7-specific features like NEON, whereas
the ARMv6 packages will need to stick to just VFP.
This change extends the cloudabi-toolchain package to also set up a
toolchain for ARMv7 properly.
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D10938
Notes:
svn path=/head/; revision=441790
|
| |
|
|
|
|
|
| |
Approved by: portmgr blanket
Notes:
svn path=/head/; revision=437936
|
| |
|
|
|
|
|
|
|
|
| |
With the release of LLVM 4.0 nearby, let's go ahead and switch over the
cloudabi-toolchain port to use the devel/llvm40 port. This allows us to
experiment with lots of C++17 features that aren't supported by
devel/llvm39 yet.
Notes:
svn path=/head/; revision=434908
|
| |
|
|
|
|
|
|
|
|
| |
Though Clang 3.9 and LLD 3.9 will not provide all the necessary bits to
create fully working binaries for ARMv6, start off by putting symlinks
to the tools in place. By the time LLVM trunk fully supports it, I'll
add an option to this port to toggle between 3.9 and trunk.
Notes:
svn path=/head/; revision=421260
|
| |
|
|
|
|
|
|
|
|
| |
So far we had to stick to the development branch, as we depend on
various features not present in 3.8. For example, a robust version of
the LLD linker. Now that 3.9.0rc1 has been packaged, make use of that
one instead.
Notes:
svn path=/head/; revision=420177
|
| |
|
|
|
|
|
|
| |
Clang already has the necessary bits on board to act as a cross compiler
for CloudABI for i686. Install the relevant symlinks for that as well.
Notes:
svn path=/head/; revision=419998
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Farnsworth: "Good news, everyone!" The latest revisions of LLVM trunk
not only have a version of LLD that creates usable binaries for x86-64
and aarch64, it also does a better job at creating Position Independent
Executables than the GNU linker.
Because PIE is going to become pretty important for some of the upcoming
projects (emulation on other OSes), I'd like to go ahead and switch the
cloudabi-toolchain port over to the latest snapshot of LLVM. My goal is
to revert back to a stable version (3.9) when available.
Switching to LLD involves patching up the Binutils ports to no longer
install the GNU linker (and remove the linker scripts that it uses). We
can then simply add a couple of extra symlinks to cloudabi-toolchain to
point to the LLD binary.
At the same time, let's switch over to using the ELF toolchain tools on
FreeBSD 11. That way we can even drop the dependency on Binutils on
those systems.
Reviewed by: bapt, emaste
Differential Revision: https://reviews.freebsd.org/D5874
Notes:
svn path=/head/; revision=413171
|
| |
|
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
Notes:
svn path=/head/; revision=412346
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the previous changes to the cloudabi-clang package brought in
more LLVM tools, the package actually became a misnomer. Most of the
tools that it installed are not part of Clang, but of LLVM instead. My
plans of extending it to also install wrappers around man(1) and
pkgconf(1) would make the naming even worse.
The only reason that the cloudabi-clang package was created in the first
place, was because we still had some of the core CloudABI libraries part
of FreeBSD Ports. Now that these libraries are part of their own package
collection, it makes more sense to squash this package together with
cloudabi-toolchain.
The nice thing about installing a wrapper around pkgconf(1) named
${gnu_triple}-pkg-config is that Autoconf now automatically picks it up.
Running ./configure --host=${gnu_triple} is enough to make it detect the
cross compiled libraries it depends on.
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D5697
Notes:
svn path=/head/; revision=411619
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I added the first copy of the CloudABI toolchain to the Ports tree,
I assumed that it would be easily possible to have a single Binutils
port that would support all of the architectures of interest. It seems
that this is not really supported, or simply awkward to use.
Let's just rename the cloudabi-binutils port to cloudabi-binutils-x86_64
and add an additional cloudabi-binutils-aarch64.
Reviewed by: emaste
Approved by: bapt
Differential Revision: https://reviews.freebsd.org/D3919
Notes:
svn path=/head/; revision=399906
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
These libraries are now provided by the CloudABI Ports collection -- not
just for FreeBSD, but a number of other operating systems. For FreeBSD,
they are provided in the form of a pkg mirror, so there is no need to
also have them in the FreeBSD Ports tree.
Approved by: bapt
Differential Revision: https://reviews.freebsd.org/D3643
Notes:
svn path=/head/; revision=396738
|
|
|
We can't reasonably expect that people want to install 7 ports to get a
working C/C++ toolchain. Add a simple metaport to install all of them in
one go.
Differential Revision: https://reviews.freebsd.org/D2929
Reviewed by: bapt
Notes:
svn path=/head/; revision=390777
|
