[Bug 234080] devel/rust-cbindgen 0.6.7_1 segfaults during configure with *** Signal 11 on FreeBSD 12.0-RELEASE
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Dec 17 22:47:32 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234080
--- Comment #4 from Kevin Reinholz <kreinholz at gmail.com> ---
@Jan Beich I followed your advice and got rust-cbindgen to accept rust-nightly
as a dependency in place of rust. However, it still segfaults with Signal 11
during configure. It seems that rust-cbindgen's mistaken expectation about stat
memory layout on FreeBSD is still in play, as detailed in the links you
provided that explain the problem quite thoroughly.
I do not know why COMPAT_FREEBSD11 enabled as an option in my kernel is
insufficient to get the libc (crate) ABI to work FreeBSD 11.x style. I suspect
more users will encounter this same problem upon upgrade to FreeBSD 12.x, given
that I have a GENERIC kernel configuration and no outlandish customizations to
my userland. (I install packages from the Ports tree and keep them up-to-date
with portmaster, pretty vanilla FreeBSD Desktop user behavior. I don't mix
packages with Ports, except as was recommending during the freebsd-update
process where rebuilding all third party installed applications was required,
but even then I've since rebuilt almost every last application from Ports in
order to track with the latest versions).
Any idea (for now) how to trick rust-cbindgen into using the correct memory
layout, or letting my system know it needs to provide FreeBSD 11.x stat memory
layout to rust-cbindgen? For now I've migrated to Chromium but I dislike the
thought of Firefox and Thunderbird being non-options on FreeBSD 12.x until libc
and/or rust makes changes to accommodate ABI-breaking differences between
FreeBSD versions. Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-gecko
mailing list