Date: Fri, 22 Aug 2014 20:59:38 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 192928] /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/local/share/chromium/chrome not found Message-ID: <bug-192928-28929-NLi0pjkEVE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192928-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-192928-28929@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=192928 Rene Ladan <rene@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rene@FreeBSD.org --- Comment #2 from Rene Ladan <rene@FreeBSD.org> --- (In reply to John Marino from comment #1) > over to maintainer group. (In reply to jan0sch from comment #0) > I've updated to chromium 36.0.1985.143_1 on two machines running 9.3-RELEASE > and get the following error on both of them if I try to start chrome: > > % chrome > /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by > /usr/local/share/chromium/chrome not found > > % strings /usr/lib/libstdc++.so.6 | grep GLIBCXX > GLIBCXX_3.4 > GLIBCXX_3.4.1 > GLIBCXX_3.4.2 > GLIBCXX_3.4.3 > GLIBCXX_3.4.4 > GLIBCXX_3.4.5 > GLIBCXX_3.4.6 > GLIBCXX_3.4.7 > GLIBCXX_3.4.8 > GLIBCXX_3.4.9 > GLIBCXX_FORCE_NEW > > % strings /usr/local/lib/gcc47/libstdc++.so.6 | grep GLIBCXX > GLIBCXX_3.4 > GLIBCXX_3.4.1 > GLIBCXX_3.4.2 > GLIBCXX_3.4.3 > GLIBCXX_3.4.4 > GLIBCXX_3.4.5 > GLIBCXX_3.4.6 > GLIBCXX_3.4.7 > GLIBCXX_3.4.8 > GLIBCXX_3.4.9 > GLIBCXX_3.4.10 > GLIBCXX_3.4.11 > GLIBCXX_3.4.12 > GLIBCXX_3.4.13 > GLIBCXX_3.4.14 > GLIBCXX_3.4.15 > GLIBCXX_3.4.16 > GLIBCXX_3.4.17 > GLIBCXX_DEBUG_MESSAGE_LENGTH > > I have tried to force the ports tree to use gcc-4.7 as described here: > https://www.freebsd.org/doc/en/articles/custom-gcc/configuring-ports-gcc.html > > But the error message didn't go away. Yeah, this also happens during build if the bundled protobuf is used instead of the ports one. But I wonder if this isn't actually a bug in the ports infrastructure or base system. -- 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-192928-28929-NLi0pjkEVE>