| 1 |
On Wed, 2004-11-10 at 09:27 -0700, Collins Richey wrote: |
| 2 |
> FYI. My system is ~x86 everything. |
| 3 |
> |
| 4 |
> I began trying to fix a problem with xscreensver (again!). After |
| 5 |
> recent emerges of gcc and glibc, xscreensaver began to cause X to |
| 6 |
> crash. A while ago (bug #64656), this was caused by needing to |
| 7 |
> reemerge gtk+. I've done this, so I thought to reemerge xorg-x11 only |
| 8 |
> to find that xorg-x11-6.7.0-r2 (my current xorg, emerged on Sep. 21) |
| 9 |
> has subsequently been masked. |
| 10 |
|
| 11 |
Masked where? Doesn't look masked to me. |
| 12 |
|
| 13 |
donnie@supernova ~ $ grep |
| 14 |
^KEY /usr/portage/x11-base/xorg-x11/xorg-x11-6.7.0-r2.ebuild |
| 15 |
/usr/portage/x11-base/xorg-x11/xorg-x11-6.7.0-r2.ebuild:KEYWORDS="arm |
| 16 |
alpha amd64 hppa ia64 mips ppc ppc64 ~sparc x86" |
| 17 |
donnie@supernova ~ $ grep xorg /usr/portage/profiles/package.mask | grep |
| 18 |
-v '^#' |
| 19 |
=x11-base/xorg-x11-6.8.0-r2 |
| 20 |
|
| 21 |
> When I attemp to emerge xorg-x11, I get |
| 22 |
> xorg-x11-6.7.0-r1 which will not compile due to the same problem |
| 23 |
> reported in bug #20395 (glxinfo unable to compile because of libGLU |
| 24 |
> errors) which was closed as invalid for xorg-x11-6.7.0-r2. |
| 25 |
|
| 26 |
6.7.0-r1 isn't even in portage. Where are you getting this? |
| 27 |
|
| 28 |
> I'm |
| 29 |
> currently running gcc-3.4.3 and glibc-2.3.4.20041102. I don't find any |
| 30 |
> other bugs relevant to me. Some people have reported "unabled to |
| 31 |
> compile" with gcc-3.4.3, but I don't have that problem. |
| 32 |
> |
| 33 |
> Any suggestions on how to proceed? |
| 34 |
> |
Archives