https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259799
--- Comment #36 from Mark Millard <marklmi26-f...@yahoo.com> ---
(In reply to Mark Millard from comment #35)
I've got things updated and past the issues that I'd run
into.
# uname -apKU
FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22
main-n250972-319e9fc642a1-dirty: Tue Nov 23 12:25:36 PST 2021
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
arm64 aarch64 1400042 1400042
(The other systems are based on the same source.)
The following is based on a chroot to an armv7 system
on a Cortex-A72 (so: aarch64) system.
I established an updated rust: 1.56 in poudriere jail main-CA7
via poudriere-devel. I then added:
# git -C /usr/ports diff /usr/ports/devel/rust-cbindgen/Makefile
diff --git a/devel/rust-cbindgen/Makefile b/devel/rust-cbindgen/Makefile
index 79d4335cf986..df7c504116c5 100644
--- a/devel/rust-cbindgen/Makefile
+++ b/devel/rust-cbindgen/Makefile
@@ -67,4 +67,8 @@ CARGO_CRATES= ansi_term-0.11.0 \
winapi-i686-pc-windows-gnu-0.4.0 \
winapi-x86_64-pc-windows-gnu-0.4.0
+.if ${ARCH:Marmv?}
+MAKE_JOBS_UNSAFE=
+.endif
+
.include <bsd.port.mk>
and attempted:
poudriere bulk -j main-CA7 -w devel/rust-cbindgen
(This does not require any more ports than required
for rust itself.)
The result was a "SIGSEGV: invalid memory reference" :
error: could not compile `tempfile`
Caused by:
process didn't exit successfully: `CARGO=/usr/local/bin/cargo
CARGO_CRATE_NAME=tempfile
CARGO_MANIFEST_DIR=/wrkdirs/usr/ports/devel/rust-cbindgen/work/cbindgen-0.20.0/cargo-crates/tempfile-3.1.0
CARGO_PKG_AUTHORS='Steven Allen <ste...@stebalien.com>:The Rust Project
Developers:Ashley Mannix <ashleyman...@live.com.au>:Jason White
<jason...@gmail.com>' CARGO_PKG_DESCRIPTION='A library for managing temporary
files and directories.'
CARGO_PKG_HOMEPAGE='http://stebalien.com/projects/tempfile-rs'
CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE=''
CARGO_PKG_NAME=tempfile
CARGO_PKG_REPOSITORY='https://github.com/Stebalien/tempfile'
CARGO_PKG_VERSION=3.1.0 CARGO_PKG_VERSION_MAJOR=3 CARGO_PKG_VERSION_MINOR=1
CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE=''
LD_LIBRARY_PATH='/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/debug/deps:/usr/local/lib'
/usr/local/bin/rustc --crate-name tempfile --edition=2018
/wrkdirs/usr/ports/devel/rust-cbindgen/work/cbindgen-0.20.0/cargo-crates/tempfile-3.1.0/src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib
--emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C
metadata=8c80968e1c70792f -C extra-filename=-8c80968e1c70792f --out-dir
/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/armv7-unknown-freebsd/debug/deps
--target armv7-unknown-freebsd -C linker=cc -L
dependency=/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/armv7-unknown-freebsd/debug/deps
-L dependency=/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/debug/deps
--extern
cfg_if=/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/armv7-unknown-freebsd/debug/deps/libcfg_if-bcb77f88a4cb1033.rmeta
--extern
libc=/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/armv7-unknown-freebsd/debug/deps/liblibc-9cfeb93970e2f28b.rmeta
--extern
rand=/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/armv7-unknown-freebsd/debug/deps/librand-521a6a5a702772ce.rmeta
--extern
remove_dir_all=/wrkdirs/usr/ports/devel/rust-cbindgen/work/target/armv7-unknown-freebsd/debug/deps/libremove_dir_all-eb5202f50395c473.rmeta
--cap-lints warn -C target-cpu=cortex-a7 -C link-arg=-fstack-protector-strong`
(signal: 11, SIGSEGV: invalid memory reference)
*** Error code 101
I'll see if I can build rust with debug symbols in order
to get a useful backtrace from a .core file --but I doubt
that I'll be able to build such in a armv7-ish context.
For reference:
My variant of top reported for the devel/rust-cbindgen time frame.
last pid: . . .; load averages: . . . MaxObs: 3.51, 1.20, 0.74
I expect that the numbers would be a lot larger if the MAKE_JOBS_UNSAFE=
had not worked: the system has 16 cores.
--
You are receiving this mail because:
You are on the CC list for the bug.
