non port: devel/wasi-libcxx/Makefile |
Number of commits found: 12 |
Wednesday, 27 Mar 2024
|
18:57 Charlie Li (vishwin)
devel/wasi-libcxx: explicitly disable LIBCXXABI_USE_LLVM_UNWINDER
LLVM 18 enables this by default, which is not wanted here. This is
effectively a no-op for other LLVM versions.
Context: https://github.com/WebAssembly/wasi-sdk/pull/377
c6c4482 |
Tuesday, 21 Nov 2023
|
17:51 Antoine Brodin (antoine)
devel/wasi-libcxx: fix PKGBASE collision
2a25004 |
Monday, 20 Nov 2023
|
21:32 Charlie Li (vishwin)
wasi: update libc to sdk-20 and modularise LLVM bits
wasi-libcxx and wasi-compiler-rt now meta ports (similar to u-boot);
the build process is the same for each LLVM version so child ports
are minimal. Minimum supported LLVM version is 12, thus its
corresponding child ports are resurrected and LLVM 11 child ports
are removed.
Since all supported LLVM versions are made available at once, remove
restriction in bsd.gecko.mk and switch to USES=llvm throughout. LTO
on gecko ports should now work with later LLVM versions so long as
${DEFAULT_VERSIONS} is set properly and matches the LLVM used in
rust (if not using the PORT_LLVM option).
Reviewed by: brooks (LLVM ports interactions)
Tested by: Eric Camachat <eric[at]camachat[dot]org>
Approved by: maintainer timeout (gecko@ portion, 2+ weeks)
PR: 274896
Differential Revision: https://reviews.freebsd.org/D40098
e38b385 |
Sunday, 9 Oct 2022
|
14:19 Charlie Li (vishwin)
devel/wasi-*: take maintainership
These have to be coordinated with gecko@.
Approved by: mentors (implicit)
6ad958d |
11:56 Fernando Apesteguía (fernape)
*/*: Release ports from maintainership
Maintainer releases all his ports.
PR: 266871
Reported by: unrelentingtech <greg@unrelenting.technology>
f57221a |
Wednesday, 7 Sep 2022
|
21:10 Stefan Eßer (se)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)
b7f0544 |
Tuesday, 8 Feb 2022
|
19:26 Christoph Moench-Tegeder (cmt)
www/firefox: unbreak after b00578b9b208
the webasm components must follow llvm (the llvm we use for building
firefox), and wasi-compiler-rt and wasi-libcxx are really just
llvm components and should be at the same version as the llvm we need.
51e8257 |
Wednesday, 24 Nov 2021
|
20:58 Christoph Moench-Tegeder (cmt)
devel/wasi-libcxx: actually disable exceptions
This port was accidentially using the base system compiler for some
parts of the configure stages - which gives wrong results in the
compiler feature tests, as base clang on FreeBSD 13.0 (llvm 11) does
not know about the wasm32 target.
Worse, even with the correct compiler some of the feature tests depend
on a present and usable libc++ for the wasi target, which we don't
have yet (this port will build one, but before...).
The end result was that the build system failed to figure out the
compiler flags for disabling exceptions (-fno-exceptions in clang's
case) and built the wasm libc++ with exceptions enabled. But exceptions
are not (yet) supported in wasi-sdk, so trying to build any code against
this wasm libc++ failed with linker errors like
wasm-ld: error:
/usr/local/share/wasi-sysroot/lib/wasm32-wasi/libc++.a(string.cpp.o): undefined
symbol: __cxa_allocate_exception
wasm-ld: error:
/usr/local/share/wasi-sysroot/lib/wasm32-wasi/libc++.a(string.cpp.o): undefined
symbol: __cxa_throw
To solve that, we have to force the configure stages to use the correct
compiler by pushing CC/CXX and related variables into CONFIGURE_ENV
and specify the results of the compiler feature tests via cmake
arguments. That is a horrible workaround, but short of a full bootstrap
build, I can't see any other solution to the chicken-and-egg problem
with wasi-libcxx requiring a functional wasi-libc++ to build.
PR: 260005
Approved by: greg at unrelenting dot technology (maintainer)
bf14389 |
Thursday, 21 Oct 2021
|
15:46 Mikael Urankar (mikael) Author: Greg V
devel/wasi-libcxx: Update to 13.0.0.
Differential Revision: https://reviews.freebsd.org/D32441
1b1f3cd |
Wednesday, 7 Apr 2021
|
08:09 Mathieu Arnold (mat)
One more small cleanup, forgotten yesterday.
Reported by: lwhsu
cf118cc |
Tuesday, 6 Apr 2021
|
14:31 Mathieu Arnold (mat)
Remove # $FreeBSD$ from Makefiles.
305f148 |
Monday, 2 Nov 2020
|
15:58 mikael
devel/wasi-compiler-rt11, wasi-libc, wasi-libcxx: New ports for WebAssembly
System Interface (WASI) libc, clang builtins (compiler-rt), libc++, libcxxabi
WASI is a "syscall" interface for WebAssembly, significantly inspired by
CloudABI.
It is supported in clang 8 and up, but to actually build C programs,
it needs clang builtins and the libc/sysroot. And for C++, also libc++ and
libcxxabi.
Submitted by: Greg V <greg%unrelenting.technology>
Differential Revision: https://reviews.freebsd.org/D22960
|
Number of commits found: 12 |