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
dist/include/nsStyleStruct.h:1896:3: error: unknown type name 'StyleFillRule'
dist/include/nsStyleStruct.h:2134:12: error: no type named 'StyleDisplay' in namespace 'mozilla'
PR: 229893
Reported by: yuripv
Obtained from: upstream
dist/include/nsStyleStruct.h:1896:3: error: unknown type name 'StyleFillRule', err: true
dist/include/nsStyleStruct.h:2134:12: error: no type named 'StyleDisplay' in namespace 'mozilla', err: true
PR: 229893
Reported by: Piotr Kubaj, cmt
Obtained from: upstream
Pointy hat to: jbeich
Standardizing on one Clang version makes stability more predictable
across supported FreeBSD versions. As a side effect performance may
suffer some improvement. This also makes it easier to enable LTO as
old LLD versions are more buggy.
Userland probes are only supported on Tier1 architectures. Even though
powerpc* should support dtrace -G may crash on C++ files built by GCC.
DTRACE option is still exposed as long as dtrace(1) binary is present
for easier debugging of libdtrace.
PR: 221641 224271
Release notes:
* https://blog.rust-lang.org/2018/07/20/Rust-1.27.2.html
* https://blog.rust-lang.org/2018/08/02/Rust-1.28.html
* https://blog.rust-lang.org/2018/09/13/Rust-1.29.html
Up to and including Rust 1.27.x, the Rust build system shelled out to
a configure script to detect the presence and usability of libunwind.
Since Rust 1.28.0, it's using a static result in a `build.rs` file and
expects libunwind to be used. It was not the case on FreeBSD so far, so
we need a patch to this `build.rs` to disable that. We still need to
study if the FreeBSD port should use libunwind and what to do with this
patch. But this problem prevented the update to Rust 1.28.0 already, so
enough delay.
The update also comes with a patch to a few `USE_GECKO`-based ports such
as Firefox [1]. Their configure script has some asumptions on the output
of `rustc --print target-list` which are not true anymore. The patch was
already committed upstream.
The aarch64 version is still marked as BROKEN because I didn't find the
time to work on it. As a consequence, there is also no aarch64 bootstrap
for Rust 1.29.0.
PR: 229826
Approved by: jbeich [1]
Obtained from: https://bugzilla.mozilla.org/show_bug.cgi?id=1479540 [1]
Differential Revision: https://reviews.freebsd.org/D17178
Change x11/xorgproto to become a build time dependency when added to
USE_XORG. Change the dependency to be on the port, rather than a file the
port installs.
Fix fallout.
Bump portrevision on depending ports.
PR: 230909
Reviewed by: eadler
Approved by: portmgr (antoine)
Obtained from: https://github.com/FreeBSDDesktop/freebsd-ports/tree/feature/xorgproto
exp-run: antoine
Differential Revision: https://reviews.freebsd.org/D16906
Many extensions on addons.mozilla.org aren't listed or updated due to
platform whitelist abuse. On DragonFly the search is broken because
such a platform isn't recognized.
PR: 226919
Reported by: Graham Perrin
ipc/chromium/src/base/process_util_linux.cc:39:23: error: no member named 'fork_delegate' in 'base::LaunchOptions'
pid_t pid = options.fork_delegate ? options.fork_delegate->Fork() : fork();
~~~~~~~ ^
ipc/chromium/src/base/process_util_linux.cc:39:47: error: no member named 'fork_delegate' in 'base::LaunchOptions'
pid_t pid = options.fork_delegate ? options.fork_delegate->Fork() : fork();
~~~~~~~ ^