public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chen Huan <chenhuan0@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Failed to emerge xulrunner-1.9.2.4
Date: Thu, 24 Jun 2010 19:05:11 +0800	[thread overview]
Message-ID: <AANLkTikNCOw2LYcsj2KDI02dNh5Sui2zEyGIpCWWYdGN@mail.gmail.com> (raw)
In-Reply-To: <hvt85v$oik$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

thanks, it is the problem

2010/6/23 walt <w41ter@gmail.com>

> On 06/22/2010 10:01 PM, Chen Huan wrote:
>
>> When I emerge xulrunner-1.9.2.4 and mozilla-firefox-3.6.4,xulrunner cannot
>> be emerged, here is the error message:
>>
>> ./../../dist/bin/js: /usr/lib/libstdc++.so.6: version `CXXABI_1.3' not
>> found (required by ./../../dist/bin/js)
>> ./../../dist/bin/js: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4' not
>> found (required by ./../../dist/bin/js)
>>
>
>  Portage 2.1.8.3 (default/linux/x86/10.0/desktop/gnome, gcc-4.3.4,
>>
>
> This is a little confusing unless you've been through it before.  I expect
> that
> portage has recently installed gcc-4.4.3 (or 4.4.4 on ~x86) so you now have
> (at
> least) two versions of gcc on your machine, but you are still using the
> older
> gcc-4.3.4.
>
> The point is that you now have (at least) two versions of libstdc++.so.6
> because
> each version of gcc installs its own version of libstdc++.
>
> Somehow the xulrunner build is trying to use both versions of
> libstdc++.so.6
> (I don't know why, but it probably involves .la files, as usual) so I
> suggest
> that you switch to the new gcc-4.4.3 (or 4.4.4) like this:
>
> #gcc-config --list-profiles
> [1] i686-pc-linux-gnu-4.3.4
> [2] i686-pc-linux-gnu-4.4.3 *    <----- (I'm already using the newer
> version)
>
> #gcc-config 1
>  * Switching native-compiler to i686-pc-linux-gnu-4.3.4 ...
>
> #gcc-config 2
>  * Switching native-compiler to i686-pc-linux-gnu-4.4.3 ...
>
> After you switch, you probably should run
> #fix_libtool_files.sh 4.3.4
>  * Scanning libtool files for hardcoded gcc library paths...
> cat: ld.so.conf.d/*.conf: No such file or directory
>  *   [1/5] Scanning /lib ...
>  *   [2/5] Scanning /usr/lib ...
>  *   [3/5] Scanning /usr/games/lib ...
>  *   [4/5] Scanning /usr/i686-pc-linux-gnu/lib ...
>  *   [5/5] Scanning /usr/local/lib ...
>
>
>

[-- Attachment #2: Type: text/html, Size: 2616 bytes --]

      reply	other threads:[~2010-06-24 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikhbXaWtJE9iWEJsgtTsLAXH2vr3RAQ_yTbyqdk@mail.gmail.com>
2010-06-23 15:10 ` [gentoo-user] Re: Failed to emerge xulrunner-1.9.2.4 walt
2010-06-24 11:05   ` Chen Huan [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=AANLkTikNCOw2LYcsj2KDI02dNh5Sui2zEyGIpCWWYdGN@mail.gmail.com \
    --to=chenhuan0@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