| 1 |
Duncan wrote: |
| 2 |
> Hamish Marson posted <1140713563.16708.26.camel@ballbreaker>, excerpted |
| 3 |
> below, on Thu, 23 Feb 2006 16:52:43 +0000: |
| 4 |
> |
| 5 |
>> Sigh... Much hacking later... The damn things disappear!!! OK. I |
| 6 |
>> re-emerged a lot... Update xorg-x11 as well because mythtv 0.19 needs qt |
| 7 |
>> with opengl support... And my symlinks disappear... So I play with |
| 8 |
>> eselect a bit & putting set -x in the relevant routins in |
| 9 |
>> /usr/share/eselect/modules/opengl.eselect reveals that eselect is busy |
| 10 |
>> trying to symlink opengl libs from /usr/lib32 which don't exist & |
| 11 |
>> ignoring lib64... |
| 12 |
>> |
| 13 |
>> Damn... Where is this stuff configured for eselect to do that? |
| 14 |
> |
| 15 |
> Isn't eselect still ~amd64? This is probably one of the reasons. |
| 16 |
> |
| 17 |
> $earch app-admin/eselect |
| 18 |
> eselect-0.9.6[0]: |
| 19 |
> eselect-1.0_rc1[0]: |
| 20 |
> eselect-1.0_rc2[0]: |
| 21 |
> eselect-1.0[0]: ~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 |
| 22 |
> |
| 23 |
> Yes... nothing stable on any arch. Only ~arch for everything. (earch is |
| 24 |
> a script I picked up on the dev list. As you can see, it lists the |
| 25 |
> versions of a package [and the slot, 0 above as eselect is unslotted] with |
| 26 |
> the associated arch keywording.) |
| 27 |
> |
| 28 |
> Those running the default multilib amd64 profiles who've upgraded gcc |
| 29 |
> since they've merged eselect are likely aware of another issue as well. |
| 30 |
> eselect compiler doesn't yet properly manage the 32-bit compiler |
| 31 |
> selection, when gcc is upgraded, so if the upgrade is in the same slot (as |
| 32 |
> is the case every time we upgrade the weekly gcc-4.1 cvs snapshots, for |
| 33 |
> those running it), the 32-bit compiler ends up pointing at the previous |
| 34 |
> version for that slot, which no longer exists! eselect compiler must be |
| 35 |
> run manually to switch to the new 32-bit gcc. Likewise, the old compiler |
| 36 |
> profile file isn't removed when the old gcc is unmerged, so eselect |
| 37 |
> continues to list stale gcc versions as choices until the associated |
| 38 |
> profile is removed manually. |
| 39 |
> |
| 40 |
> Folks like me that run a ~arch system should expect such less than smooth |
| 41 |
> operation, from time to time, and in fact many of us enjoy the challenge |
| 42 |
> (I definitely do), so it's no big deal, even if it /does/ get slightly |
| 43 |
> frustrating from time to time. It's all in the game! |
| 44 |
> |
| 45 |
|
| 46 |
Any chance someone could put together an ebuild for earch so those of us |
| 47 |
who missed it on the dev list can install it? While I realize I could |
| 48 |
go digging through ebuilds one by one to see what's x86 and ~amd64, it |
| 49 |
would be easier to just have a script pull out that info for me. I'd |
| 50 |
like to help wherever I can in getting x86/~amd64 stuff tested and fixed. |
| 51 |
-- |
| 52 |
D. Wokan |
| 53 |
-- |
| 54 |
gentoo-amd64@g.o mailing list |
Archives