This new version of cloudabi-utils now installs a library called
libcloudabi. This library contains native ports of some of the APIs that
are currently provided as part of CloudABI's runtime. These used to be
built into cloudabi-run itself, but are now exposed as well.
As cloudabi-utils is now becoming more complex, it now uses CMake as its
build system. We can now remove our custom build targets. We do need to
make sure to override CMAKE_INSTALL_MANDIR, as it is set to share/man by
default. I'm slightly amazed that this isn't done by default.
Reviewed by: beat
Differential Revision: https://reviews.freebsd.org/D4176
Compared to version 0.5, this package is identical, except that it now
provides support for aarch64.
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D3976
CloudABI now has its own package collection for FreeBSD and Debian based
systems (https://github.com/NuxiNL/cloudabi-ports/). This package
collection will only contain software that is cross compiled for
CloudABI -- no FreeBSD native executables.
I would like to go ahead and remove all ports that overlap with the
packages provided by CloudABI Ports. Let's start off by updating
cloudabi-utils to version 0.5. This version no longer depends on the
CloudABI toolchain, as it now ships with a precompiled copy of the
trampoline executable.
Once this is done, I can go ahead and remove devel/cloudabi-cloudlibc,
devel/cloudabi-compiler-rt, devel/cloudabi-libc++,
devel/cloudabi-libc++abi and devel/cloudabi-libunwind/.
Approved by: bapt
Differential Revision: https://reviews.freebsd.org/D3616
A new version of cloudlibc and cloudabi-utils has been released, to
catch up with ABI changes (due to the import into FreeBSD HEAD). Bump
these ports up to v0.4.
While there, upgrade the LLVM packages. It looks like the LLVM project
is finally releasing tarballs itself, meaning we can use those instead
of requiring me to host them myself. Update the ports to use a common
Makefile (cloudabi-libc++/Makefile.common) to set the PORTVERSION,
MASTER_SITES, etc.
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D3332
Due to the CloudABI code being reviewed before hitting the tree, some
minor ABI tweaks are made in a couple of places, while we still can.
Unfortunately, this means that the previous version of cloudlibc now
generates binaries that are not compatible with the latest kernel
sources.
Roll a new release that makes the toolchain compatible with what's in
FreeBSD HEAD.
Summary:
It looks like we forgot to add '${SETENV} ${MAKE_ENV}' to the build
script. Right now it ignores the compiler entirely.
Furthermore, regardless of whether a C11 compiler is being used, the
build will fail, for the reason that some C11 headers such as
<stdnoreturn.h> are being used in the code. Instead of trying to fix
that, simply disable this port on FreeBSD <10.1. I have no intent on
ever getting CloudABI to work on FreeBSD 9.
Reviewers: bapt
Reviewed By: bapt
Differential Revision: https://reviews.freebsd.org/D3077
Summary:
Though CloudABI programs can simply be started from the command line
like any UNIX process, the preferred way for starting them is using the
cloudabi-run utility.
cloudabi-run parses a YAML file that contains the configuration for the
program that you want to run. Special tags can be used in the YAML file
to indicate that the program depends on a resources (a socket or a
file). cloudabi-run then attempts to obtain these resources and startes
the program for you.
The end result is that it's possible to build software that looks like
traditional UNIX software (executable + config file), but still gets run
in this completely sandboxed environment.
Reviewers: bapt
Reviewed By: bapt
Differential Revision: https://reviews.freebsd.org/D3067
