Date: Mon, 22 Jul 2019 10:36:40 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 239379] devel/protobuf: pthread include fails, breaks net/mosh Message-ID: <bug-239379-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239379 Bug ID: 239379 Summary: devel/protobuf: pthread include fails, breaks net/mosh Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: m.bueker@berlin.de CC: sunpoet@FreeBSD.org, zi@FreeBSD.org CC: sunpoet@FreeBSD.org, zi@FreeBSD.org The root cause of bug #239038 appears to be that protobuf compilation (no longer?) includes pthread in the way that is needed for net/mosh to functio= n. Compare the error message: [libprotobuf FATAL google/protobuf/generated_message_util.cc:809] CHECK failed: (scc->visit_status.load(std::memory_order_relaxed)) =3D=3D (SCCInfoBase::kRunning): to the one reported in https://stackoverflow.com/questions/52890529/fatalexception-thrown-by-proto= buf-library-on-instantiation-of-message: [libprotobuf FATAL /myproj/protobuf/src/google/protobuf/generated_message_util.cc:785] CHECK failed: (scc->visit_status.load(std::memory_order_relaxed)) =3D=3D (SCCInfoBase::kRunning): In that stackoverflow discussion, the solution is to add "--no-as-needed" before "-pthread" to the linker flags for protobuf. This suggests that a similar tweak to the protobuf build instructions in FreeBSD ports could also help. I am not sufficiently familiar with ports to= try this myself. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239379-7788>