From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: glibmm 2.20.1 emerge fails to compile
Date: Mon, 28 Sep 2009 15:02:36 +0000 (UTC) [thread overview]
Message-ID: <h9qj6b$ue4$1@ger.gmane.org> (raw)
In-Reply-To: h9q8tn$t02$1@ger.gmane.org
On 2009-09-28, walt <w41ter@gmail.com> wrote:
> On 09/27/2009 09:38 PM, Grant Edwards wrote:
>> I tried doing an upgrade (the usual emerge -auvND world), and
>> it choked on glibmm 2.20.1. The compile failed the basic error
>> seems to be this:
>>
>> generate_defs_glib.o: In function `main':
>> generate_defs_glib.cc:(.text+0x6b): undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, int)'
[...]
> Those undefined references are supplied by libstdc++, so it
> looks like you have a classic case of duelling library
> versions.
>
> The error messages mention gcc-3.4.6, which is actually quite
> old now, so perhaps you've switched to gcc-4.x.x now?
Yes! I suspected that was the issue, but I had missed noticing
the 3.4.6 in some of the libstdc++ paths.
> The fix is to go back and re-emerge all packages that linked
> against the old libstdc++.
Thanks. I figured it was something like that.
> One way to find them is to run fix_libtool_files.sh and note
> which ones get fixed. You still need to re-emerge those
> packages, though, if you're now using gcc-4.x
Yes, I'm now using gcc 4.
> I would actually just grep through all the .la files for
> "3.4.6" (assuming that's your *old* version of gcc) and
> re-emerge the packages that own those files. Maybe someone
> else knows an easier way.
I'll try fix_libtool_files.sh first, then go from there.
--
Grant
prev parent reply other threads:[~2009-09-28 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 4:38 [gentoo-user] glibmm 2.20.1 emerge fails to compile Grant Edwards
2009-09-28 12:07 ` [gentoo-user] " walt
2009-09-28 15:02 ` Grant Edwards [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h9qj6b$ue4$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox