Date: Sat, 13 Nov 2021 10:08:43 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 259799] devel/rust-cbindgen: armv6: build using "make" fails, using "cargo build --release -j 1" works Message-ID: <bug-259799-21738-KDzxRAv2pz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259799-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-259799-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259799 --- Comment #27 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Martin Birgmeier from comment #26) Remember that my test context goes back to /usr/ports as of: # ~/fbsd-based-on-what-commit.sh=20 branch: main merge-base: faf17873c10627379554b4c5f7a66539b347f221 merge-base: CommitDate: 2021-10-23 21:38:18 +0000 faf17873c106 (HEAD -> main, freebsd/main, freebsd/HEAD) lang/gnatdroid-binutils: Add CPE information n563214 (--first-parent --count for merge-base) It turns out that a rustc.core file was generated and gdb reports: Core was generated by `/usr/local/bin/rustc --crate-name trust_dns_proto --edition=3D2018 /wrkdirs/usr/po'. but the rustc in my environment is not a debug build and I do not get a reasoonable backtrace to report. (I do not now that a 32-bit debug-build of rustc is even possible. I'm not even sure for 64-bit aarch64.) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259799-21738-KDzxRAv2pz>