Date: Mon, 13 Apr 2015 21:31:26 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 196078] [patch] unbreak x11-fm/sushi build on FreeBSD 8 Message-ID: <bug-196078-6497-WPOT5VgYfX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196078-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-196078-6497@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=196078 Don Lewis <truckman@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #4 from Don Lewis <truckman@FreeBSD.org> --- If I convert lang/gjs and lang/spidermonkey24 from USES=compiler:c11 to USES=compiler:c++11-lib, sushi builds and appears to run correctly without needing any modification. I can't totally verify functionality because I still can't start a GNOME session. On FreeBSD 8 and 9, this change causes gjs and spidermonkey24 to be build with gcc 4.8 from ports and link to its bundled copy of libstdc++ instead of being built with clang and linked the version of libstdc++ in base. Converting sushi to USES=compiler:c11 and forcing it to link to libstdc++ is the wrong approach because sushi appears to be entirely written in C and does not directly need a C++ library. The link errors were happening because libwebkitgtk-3.0 requires the newer libstdc++ from the gcc 4.8 port, but the other libraries were linked to the base libstdc++, and the version chosen by the linker when building sushi seems depend on the order of the libraries since it wasn't being forced to pick the gcc 4.8 port version by sushi. The libgraphite2 library is still linked to libstdc++ in base but doesn't seem to cause any problems. -- 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-196078-6497-WPOT5VgYfX>