Date: Wed, 19 Dec 2018 00:39:37 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 234080] devel/rust-cbindgen 0.6.7_1 segfaults during configure with *** Signal 11 on FreeBSD 12.0-RELEASE Message-ID: <bug-234080-21738-rNwPyCGajn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234080-21738@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234080 Kevin Reinholz <kreinholz@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug Status|New |Closed --- Comment #12 from Kevin Reinholz <kreinholz@gmail.com> --- @Tobias Kortkamp & @Jan Beich, you're geniuses! :) After removal of the Port installed openssl and rebuilding of all Ports dependent upon it to use base openssl, to include rebuilding rust-1.31.0 and replacing rust-nightly with it, ldd shows no more conflict re ssl libs in cargo: Lahan% ldd /usr/local/bin/cargo /usr/local/bin/cargo: libgit2.so.27 => /usr/local/bin/../lib/libgit2.so.27 (0x800671000) libssh2.so.1 => /usr/local/bin/../lib/libssh2.so.1 (0x800766000) libssl.so.111 => /usr/lib/libssl.so.111 (0x8016eb000) libcrypto.so.111 => /lib/libcrypto.so.111 (0x801780000) libz.so.6 => /lib/libz.so.6 (0x800793000) libthr.so.3 => /lib/libthr.so.3 (0x8007ad000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x8007d8000) libc.so.7 => /lib/libc.so.7 (0x800248000) libm.so.5 => /lib/libm.so.5 (0x801a6d000) librt.so.1 => /usr/lib/librt.so.1 (0x8007f0000) libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x801a9f000) Lahan% rust-cbindgen built happily from Ports without complaint. Just in case, I had started a script and built it within to log its progress in the event any errors occurred, but "Finished release [optimized] target(s) in 7m 13s" and all is good! I've currently got firefox rebuilding/updating from Ports, quite happily I might add. (No configure errors or missing dependencies). I think this is an excellent cautionary tale about the dangers of the Port installed openssl and perhaps something that should get some attention, as I had /etc/make.conf set to use the Port openssl since 2016, something which oddly enough only after upgrade to FreeBSD 12.0 seemed to cause a problem. (It's frankly amazing that it didn't cause problems before, but perhaps Ports happily built against the Port openssl instead of the base one up until now, when cargo at least become polluted and linked against the competing ssl libs). At any rate I'm happy to have fixed this issue with my system, and hope this might help others if they experience a similar problem. Thanks again for your help! Issue resolved! -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234080-21738-rNwPyCGajn>