I actually fixed the glibc DEPENDS around the time I sent the email, and I didn't realize there were so many other packages that directly depend on it. glibc depends on it for crosscompiler support (that's just from the comment in the ebuild made by vapier. I actually don't understand why myself, but crossdev is his baby.)

In that case, I definitely recommend unmasking sys-devel/gcc-config as well (via /etc/portage/package.unask) so the compatibility wrapper will be installed, too.

I'll work at getting all those other packages fixed to use toolchain- funcs.eclass or use eselect-compiler directly, but if anyone wants to jump in, be my guest.

--Jeremy

On May 31, 2006, at 06:57 , Kevin F. Quinn wrote:

On Tue, 30 May 2006 12:43:34 -0700
Jeremy Huddleston <[EMAIL PROTECTED]> wrote:

then emerge eselect-compiler and unmerge gcc-config.  If you need
backwards compatibility, you can also add the following to
package.unmask:
sys-devel/gcc-config

The following depend on sys-devel/gcc-config (only); of particular note
are sys-libs/glibc, syslibs/libstdc++ and syslibs/libffi:


sys-devel/distcc 2.18.3-r10 2.16-r2 2.18.3-r6 2.18.3-r8 2.16-r3
2.18.3-r7

sys-devel/gcc-powerpc64 3.4.4

sys-devel/gcc-sparc64 3.3.6 3.4.6 3.3.5 3.4.5

sys-devel/gcc-hppa64 3.3.2 3.4.5 3.3.2-r1

sys-devel/gcc-mips64 3.4.5 3.4.4

media-gfx/sam2p 0.44

sys-process/supervise-scripts 3.5

sys-apps/ucspi-proxy 0.95

sys-libs/glibc 2.3.5-r2 2.3.5 2.3.6-r1 2.4-r1 2.3.6-r3 2.3.5-r1 2.4-r3
2.3.4.20041102-r2 2.3.5-r3 2.3.6 2.3.6-r2 2.4-r2 2.3.4.20050125-r1
2.3.6-r4

sys-libs/libstdc++-v3 3.3.3-r1 3.3.4 3.3.6

net-mail/qtools 0.56

net-mail/relay-ctrl 3.1.1-r2

dev-lang/ccc 6.5.9.001-r1 6.5.9.001-r3 6.5.9.001 6.5.6.002 6.5.9.001-r2

dev-lang/cxx 6.5.9.31-r1 6.5.9.31

dev-lang/cfal 1.2.0.4

dev-libs/libffi 3.4.1-r1 3.4.1 3.3.5 3.4.3


So unmerging gcc-config will cause portage to try to pull it back in on
"emerge -puDv world" etc.  Many of them use gcc-config to get info
about the compiler (they should probably be using toolchain-funcs, I
think). I don't really see why several of these depend on gcc-config
(e.g. glibc!), but maybe I'm missing something.

--
Kevin F. Quinn

--
[email protected] mailing list

Reply via email to