Date: Sat, 04 Apr 2015 16:21:55 +0200 From: Guido Falsi <mad@madpilot.net> To: jbtakk@iherebuywisely.com, stable <stable@freebsd.org> Subject: Re: GLIBCXX errors, a very few ports don't run Message-ID: <551FF383.6040505@madpilot.net> In-Reply-To: <E1YeMv0-0001Md-38@rmm6prod02.runbox.com> References: <E1YeMv0-0001Md-38@rmm6prod02.runbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/04/15 14:11, Jeffrey Bouquet wrote: > > command: lnav -s > /usr/local/lib/gcc47/libstdc++.so.6: version GLIBCXX_3.4.20 required by /usr/local/bin/lnav not found > > Script done on Sat Apr 4 04:56:17 2015 > > > ........................................................................... > 10.1-STABLE r280322 > .............................................. > gcc-4.8... > gcc-ecj-4.5 > gcc47-4.7... > gcc49-4.9... > ............................................ > Anyone know of the best practices to trim down/reconfigure the set of compilers one has installed so the > GLIBCXX/libstdc issue which sometimes appears goes away eventually, or is remedied by a libmap.conf ? > ........................................... > Or any similar fix? I have seen this happen in certain situations. It's the dynamic linker which links them to the wrong libstdc++. In your case, it looks like you have various gcc ports installed, so various libstdc++. I think your best bet is removing all gcc ports and install just one (the default one is 4.8, but you could choose to keep 4.9 if it works fine for you) and reinstall any port missing libraries. Using ports you can use "pkg check -Bn" to look for missing libraries and rebuild such ports. This should make them all use the available gcc version ad resolve the conflict. Hope this helps. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551FF383.6040505>