| 1 |
I actually fixed the glibc DEPENDS around the time I sent the email, |
| 2 |
and I didn't realize there were so many other packages that directly |
| 3 |
depend on it. glibc depends on it for crosscompiler support (that's |
| 4 |
just from the comment in the ebuild made by vapier. I actually don't |
| 5 |
understand why myself, but crossdev is his baby.) |
| 6 |
|
| 7 |
In that case, I definitely recommend unmasking sys-devel/gcc-config |
| 8 |
as well (via /etc/portage/package.unask) so the compatibility wrapper |
| 9 |
will be installed, too. |
| 10 |
|
| 11 |
I'll work at getting all those other packages fixed to use toolchain- |
| 12 |
funcs.eclass or use eselect-compiler directly, but if anyone wants to |
| 13 |
jump in, be my guest. |
| 14 |
|
| 15 |
--Jeremy |
| 16 |
|
| 17 |
On May 31, 2006, at 06:57 , Kevin F. Quinn wrote: |
| 18 |
|
| 19 |
> On Tue, 30 May 2006 12:43:34 -0700 |
| 20 |
> Jeremy Huddleston <eradicator@g.o> wrote: |
| 21 |
> |
| 22 |
>> then emerge eselect-compiler and unmerge gcc-config. If you need |
| 23 |
>> backwards compatibility, you can also add the following to |
| 24 |
>> package.unmask: |
| 25 |
>> sys-devel/gcc-config |
| 26 |
> |
| 27 |
> The following depend on sys-devel/gcc-config (only); of particular |
| 28 |
> note |
| 29 |
> are sys-libs/glibc, syslibs/libstdc++ and syslibs/libffi: |
| 30 |
> |
| 31 |
> |
| 32 |
> sys-devel/distcc 2.18.3-r10 2.16-r2 2.18.3-r6 2.18.3-r8 2.16-r3 |
| 33 |
> 2.18.3-r7 |
| 34 |
> |
| 35 |
> sys-devel/gcc-powerpc64 3.4.4 |
| 36 |
> |
| 37 |
> sys-devel/gcc-sparc64 3.3.6 3.4.6 3.3.5 3.4.5 |
| 38 |
> |
| 39 |
> sys-devel/gcc-hppa64 3.3.2 3.4.5 3.3.2-r1 |
| 40 |
> |
| 41 |
> sys-devel/gcc-mips64 3.4.5 3.4.4 |
| 42 |
> |
| 43 |
> media-gfx/sam2p 0.44 |
| 44 |
> |
| 45 |
> sys-process/supervise-scripts 3.5 |
| 46 |
> |
| 47 |
> sys-apps/ucspi-proxy 0.95 |
| 48 |
> |
| 49 |
> 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 |
| 50 |
> 2.3.4.20041102-r2 2.3.5-r3 2.3.6 2.3.6-r2 2.4-r2 2.3.4.20050125-r1 |
| 51 |
> 2.3.6-r4 |
| 52 |
> |
| 53 |
> sys-libs/libstdc++-v3 3.3.3-r1 3.3.4 3.3.6 |
| 54 |
> |
| 55 |
> net-mail/qtools 0.56 |
| 56 |
> |
| 57 |
> net-mail/relay-ctrl 3.1.1-r2 |
| 58 |
> |
| 59 |
> dev-lang/ccc 6.5.9.001-r1 6.5.9.001-r3 6.5.9.001 6.5.6.002 |
| 60 |
> 6.5.9.001-r2 |
| 61 |
> |
| 62 |
> dev-lang/cxx 6.5.9.31-r1 6.5.9.31 |
| 63 |
> |
| 64 |
> dev-lang/cfal 1.2.0.4 |
| 65 |
> |
| 66 |
> dev-libs/libffi 3.4.1-r1 3.4.1 3.3.5 3.4.3 |
| 67 |
> |
| 68 |
> |
| 69 |
> So unmerging gcc-config will cause portage to try to pull it back |
| 70 |
> in on |
| 71 |
> "emerge -puDv world" etc. Many of them use gcc-config to get info |
| 72 |
> about the compiler (they should probably be using toolchain-funcs, I |
| 73 |
> think). I don't really see why several of these depend on gcc-config |
| 74 |
> (e.g. glibc!), but maybe I'm missing something. |
| 75 |
> |
| 76 |
> -- |
| 77 |
> Kevin F. Quinn |
| 78 |
|
| 79 |
-- |
| 80 |
gentoo-amd64@g.o mailing list |
Archives