From: icephere <icephere@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: why xorg-server needs an old gcc?
Date: Sat, 21 Jul 2007 18:03:50 -0400 [thread overview]
Message-ID: <71904837-9EEC-4D98-B933-9E50F64D2A41@gmail.com> (raw)
In-Reply-To: <f7ttru$huj$1@sea.gmane.org>
Thank you very much!
My box does not have libstdc++-v3, and it is a "Compatibility
package for running binaries linked against a pre gcc 3.4 libstdc++"
Best,
ice
On Jul 21, 2007, at 5:29 PM, Remy Blank wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> b.n. wrote:
>> icephere ha scritto:
>>> When I remove "fglrx" from VIDEO_CARDS, the old gcc is not
>>> required by
>>> emerge anymore... weird
>>
>> Probably the proprietary fglrx module is still not GCC-4 compatible.
>
> - From the ati-drivers ebuild, you can see that it depends on
> =virtual/libstdc++-3.3*. And in that ebuild, you see that this can be
> provided either by =sys-libs/libstdc++-v3-3.3* or =sys-devel/gcc-3.3*.
> Why it prefers the latter is not quite clear to me, probably
> because you
> already have the gcc package installed (albeit in another slot).
>
> - -- Remy
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFGonq9CeNfIyhvXjIRAj85AJwLn3oZh5GHikSJHg6cYCNvwBtvXACfSPs/
> aCMI+fm719y1dgl/LA9LTR0=
> =y9Vf
> -----END PGP SIGNATURE-----
>
> --
> gentoo-user@gentoo.org mailing list
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-21 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 18:39 [gentoo-user] why xorg-server needs an old gcc? icephere
2007-07-21 18:50 ` [gentoo-user] " icephere
2007-07-21 21:04 ` b.n.
2007-07-21 21:29 ` Remy Blank
2007-07-21 22:03 ` icephere [this message]
2007-07-22 2:05 ` [gentoo-user] sann-find-scanner can't find my scanner Xihong Yin
2007-07-22 2:37 ` Dale
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=71904837-9EEC-4D98-B933-9E50F64D2A41@gmail.com \
--to=icephere@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