Date: Sat, 13 Nov 2021 22:49:42 +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-xnxg2KbQF6@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 #31 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #30) I have confirmed that on a Cortex-A7 (armv7) system, I also get (for example): . . . thread 'rustc' panicked at 'capacity overflow', library/alloc/src/raw_vec.rs:559:5 stack backtrace: note: Some details are omitted, run with `RUST_BACKTRACE=3Dfull` for a verb= ose backtrace. error: internal compiler error: unexpected panic note: the compiler unexpectedly panicked. this is a bug. note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=3DC-bug%2C+I-ICE%2C+T-c= ompiler&template=3Dice.md note: rustc 1.55.0 running on armv7-unknown-freebsd note: compiler flags: -C embed-bitcode=3Dno -C debuginfo=3D2 -C linker=3Dcc= -C target-cpu=3Dcortex-a7 -C link-arg=3D-fstack-protector-strong --crate-type = lib note: some of the compiler flags provided by cargo are hidden query stack during panic: #0 [trimmed_def_paths] calculating trimmed def paths #1 [lint_mod] linting module `file` #2 [analysis] running analysis passes on this crate end of query stack thread 'rustc' panicked at 'cannot panic during the backtrace function', library/std/src/../../backtrace/src/lib.rs:147:13 stack backtrace: 0: 0x2750076c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h4428caffcb182c5b 1: 0x275c9d00 - core::fmt::write::h91f4a7678561fd61 . . . 49: 0x274ee71c - <unknown> 50: 0x2783b1bc - <unknown> 51: 0x2783acd8 - pthread_create 52: 0x2783db9c - pthread_peekjoin_np 53: 0x2783db9c - pthread_peekjoin_np 54: 0x2783db9c - pthread_peekjoin_np 55: 0x2783db9c - pthread_peekjoin_np . . . pthread_peekjoin_np lines repating (but for the prefix) . . . So the issue for this is not tied to COMPATFREEBSD32 or the like. --=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-xnxg2KbQF6>