It seems some sysctl are not present if COMPAT_FREEBSD11 is missing: https://github.com/libstatgrab/libstatgrab/issues/103, why not checking if sysctl vm.stats.vm.v_cache_count suceeds (I haven't tried if it works to be honest)?

Anyway, the issue is not limited to rust. People can have the problem doing the following:

pkg add rust
make -C /usr/ports/www/firefox

The check should probably be duplicated in every consumers (cargo.mk, bsd.gecko.mk...)

In D23100#506250, @mikael.urankar_gmail.com wrote:

It seems some sysctl are not present if COMPAT_FREEBSD11 is missing: https://github.com/libstatgrab/libstatgrab/issues/103, why not checking if sysctl vm.stats.vm.v_cache_count suceeds (I haven't tried if it works to be honest)?

Anyway, the issue is not limited to rust. People can have the problem doing the following:

pkg add rust
make -C /usr/ports/www/firefox

The check should probably be duplicated in every consumers (cargo.mk, bsd.gecko.mk...)

It's ok with me to put something in cargo.mk as soon as we have a good enough check.

I have tested this patch, since I had a kernel without COMPAT_ options around and it does what it tries, this is the output in poudriere:

===========================================================================
=======================<phase: configure      >============================
===>  Configuring for rust-1.40.0
===>   FreeBSD 10 autotools fix applied to /wrkdirs/usr/ports/lang/rust/work/rustc-1.40.0-src/vendor/libssh2-sys/libssh2/config.rpath
===>   FreeBSD 10 autotools fix applied to /wrkdirs/usr/ports/lang/rust/work/rustc-1.40.0-src/vendor/backtrace-sys/src/libbacktrace/config/libtool.m4
===>   FreeBSD 10 autotools fix applied to /wrkdirs/usr/ports/lang/rust/work/rustc-1.40.0-src/vendor/backtrace-sys/src/libbacktrace/configure
Bad system call
=> Sanity check failed: kernel is missing COMPAT_FREEBSD11
=> Aborting build
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/rust
=>> Cleaning up wrkdir
===>  Cleaning for rust-1.40.0

In D23100#506966, @tobik wrote:

• Add check to cargo.mk and bsd.gecko.mk too

@madpilot Thanks for testing!

To be complete I would also have to spam it into other ports using lang/rust:

graphics/librsvg2-rust
net-im/fractal
security/suricata
security/suricata5
www/cliqz

But I am not sure if it's worth it?

IMO it's enough to patch rust, cargo.mk and gecko.mk

@jbeich Are you fine with the changes to bsd.gecko.mk ?

Looks ugly and doesn't cover runtime (see below) but I won't block landing.

$ pkg install rust ripgrep

$ truss rustc test.rs 2>&1 | tail -5
compat11.stat("(null)",0x0)                      ERR#78 'Function not implemented'
SIGNAL 12 (SIGSYS) code=SI_KERNEL
_umtx_op(0x8011f3500,UMTX_OP_WAIT,0x188aa,0x0,0x0) ERR#4 'Interrupted system call'
<thread 100951 exited>
process killed, signal = 12

$ truss rg test 2>&1 | tail -3
compat11.stat("(null)",0x0)                      ERR#78 'Function not implemented'
SIGNAL 12 (SIGSYS) code=SI_KERNEL
process killed, signal = 12

In D23100#507282, @jbeich wrote:

Looks ugly and doesn't cover runtime (see below) but I won't block landing.

$ pkg install rust ripgrep

$ truss rustc test.rs 2>&1 | tail -5
compat11.stat("(null)",0x0)                      ERR#78 'Function not implemented'
SIGNAL 12 (SIGSYS) code=SI_KERNEL
_umtx_op(0x8011f3500,UMTX_OP_WAIT,0x188aa,0x0,0x0) ERR#4 'Interrupted system call'
<thread 100951 exited>
process killed, signal = 12

$ truss rg test 2>&1 | tail -3
compat11.stat("(null)",0x0)                      ERR#78 'Function not implemented'
SIGNAL 12 (SIGSYS) code=SI_KERNEL
process killed, signal = 12

Yes, of course, but so far I have only seen people complain on Bugzilla when they are building their own stuff, i.e., kernels without COMPAT_FREEBSD11 + lang/rust and www/firefox. That same user group does not seem to use binary packages.

I suppose I could add an UPDATING entry for this too to cover all the bases but then this is as far as it should go IMHO. Then again binary package users will not read UPDATING either, so it would probably solve nothing.