Hey all,
The basic issue is that I can emerge some things, but not others, and I
can't figure out why.
So far, the main victims are cdrtools and ncurses (!!!).
Many things emerge fine (I emerged snes9x last night, and I'm doing an
emerge -uaDtv world at this moment; so far tcl, sed, groff and gcc are
emerging without errors, so have cups and samba).
However, for cdrtools I get an error in /bin/cc (compiler cannot create
executables), and in ncurses (I was desperate and tried an emerge -e
system, otherwise I had no particular reason to remerge ncurses of all
things) I got an error in /lib/cpp (fails sanity check).
Previously (a week or so ago), I had to hack my kernel source to install
the ati-drivers (after a long fight with trying to remove koutput),
because even after I reverted to normal output, files like
..tmp_kallsyms1.o.cmd were not executable by root for some reason--
which was a kind of error I never saw when originally using regular
kernel output, and on the whole just doesn't make sense to me (not to
mention worries me quite a bit).
The new Portage (2.51_rc1) keeps mentioning that ebuilds I'm upgrading
from or unmerging are inheriting 'things' illegally (from eclasses, I
think) before the emerge goes fine, which doesn't seem like a good thing.
OK, that last just seems to be informational and not so much related
(she said, in her ignorance), but the whole set of issues seems to
indicate that something very deep in the system is borked (I mean, if
ncurses won't emerge, there's a problem), but I have no idea where to
look for it (which was why I was trying the emerge -e system to see if I
could catch it).
I really don't know what to do anymore. Basic system specs are: ~x86,
kernel 2.6.8.1-ck7, gcc 3.4.2-r1 (emerging now, up from 3.4.1-r2, which
was an upgrade from -r1 last night), CFLAGS -O2 (down from -Os, which I
don't so much think was the problem, but as I said, I was desperate),
-march=athlon-xp -fomit-frame-pointer -pipe. The only CFLAG I have
recently removed (other than changing Os to O2) was -fPIC (and please
don't jump on me for having had it; I know I shouldn't have used it,
which is why I took it out). The only major system change before these
things started happening was an attempted upgrade to xorg 6.8.0, an
attempted downgrade to xorg 6.7.0-r2, an ultimate unmerge and remerge of
xorg 6.7.0-r2, and the kernel upgrade from 2.6.8.1-ck6 to 2.6.8.1-ck7.
Oh, wait... look at that. GCC is updating, and I see that I have 2
versions installed during the cleanup-- 3.4.1-r2 is being removed, but
3.4.2-r2 *and* 3.3.4-r1 (!!!) are protected.
Given that 3.4.2-r2 just did a lot of FIXING of libraries and whatnot,
is it possible that the presence of GCC 3.3.4 is the problem? I checked
gcc-config and while I do have 3 profiles (3.4.2, 3.3.4, and 3.3.3), I
appear to be using 3.4.2 as I would expect.
The issue generally seems to be with the C++ preprocessor, but I don't
know what to do about that, since g++ is in /usr/bin where it's supposed
to be. Version is g++ (GCC) 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1,
pie-8.7.6.5).
Does anybody have an idea as to how I can restore my system
to some semblance of 'stablity'? Yes, I know ~x86 is not 'stable' by
definition, but this seems a bit over-the-top. All I was trying to do
was emerge dvdrip (which requires cdrtools 2.01) and I've wound up
attempting (and failing) an emerge -e system just to accomplish that
(which I have not, yet).
Please help.
Holly
--
gentoo-user@gentoo.org mailing list
The basic issue is that I can emerge some things, but not others, and I
can't figure out why.
So far, the main victims are cdrtools and ncurses (!!!).
Many things emerge fine (I emerged snes9x last night, and I'm doing an
emerge -uaDtv world at this moment; so far tcl, sed, groff and gcc are
emerging without errors, so have cups and samba).
However, for cdrtools I get an error in /bin/cc (compiler cannot create
executables), and in ncurses (I was desperate and tried an emerge -e
system, otherwise I had no particular reason to remerge ncurses of all
things) I got an error in /lib/cpp (fails sanity check).
Previously (a week or so ago), I had to hack my kernel source to install
the ati-drivers (after a long fight with trying to remove koutput),
because even after I reverted to normal output, files like
..tmp_kallsyms1.o.cmd were not executable by root for some reason--
which was a kind of error I never saw when originally using regular
kernel output, and on the whole just doesn't make sense to me (not to
mention worries me quite a bit).
The new Portage (2.51_rc1) keeps mentioning that ebuilds I'm upgrading
from or unmerging are inheriting 'things' illegally (from eclasses, I
think) before the emerge goes fine, which doesn't seem like a good thing.
OK, that last just seems to be informational and not so much related
(she said, in her ignorance), but the whole set of issues seems to
indicate that something very deep in the system is borked (I mean, if
ncurses won't emerge, there's a problem), but I have no idea where to
look for it (which was why I was trying the emerge -e system to see if I
could catch it).
I really don't know what to do anymore. Basic system specs are: ~x86,
kernel 2.6.8.1-ck7, gcc 3.4.2-r1 (emerging now, up from 3.4.1-r2, which
was an upgrade from -r1 last night), CFLAGS -O2 (down from -Os, which I
don't so much think was the problem, but as I said, I was desperate),
-march=athlon-xp -fomit-frame-pointer -pipe. The only CFLAG I have
recently removed (other than changing Os to O2) was -fPIC (and please
don't jump on me for having had it; I know I shouldn't have used it,
which is why I took it out). The only major system change before these
things started happening was an attempted upgrade to xorg 6.8.0, an
attempted downgrade to xorg 6.7.0-r2, an ultimate unmerge and remerge of
xorg 6.7.0-r2, and the kernel upgrade from 2.6.8.1-ck6 to 2.6.8.1-ck7.
Oh, wait... look at that. GCC is updating, and I see that I have 2
versions installed during the cleanup-- 3.4.1-r2 is being removed, but
3.4.2-r2 *and* 3.3.4-r1 (!!!) are protected.
Given that 3.4.2-r2 just did a lot of FIXING of libraries and whatnot,
is it possible that the presence of GCC 3.3.4 is the problem? I checked
gcc-config and while I do have 3 profiles (3.4.2, 3.3.4, and 3.3.3), I
appear to be using 3.4.2 as I would expect.
The issue generally seems to be with the C++ preprocessor, but I don't
know what to do about that, since g++ is in /usr/bin where it's supposed
to be. Version is g++ (GCC) 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1,
pie-8.7.6.5).
Does anybody have an idea as to how I can restore my system
to some semblance of 'stablity'? Yes, I know ~x86 is not 'stable' by
definition, but this seems a bit over-the-top. All I was trying to do
was emerge dvdrip (which requires cdrtools 2.01) and I've wound up
attempting (and failing) an emerge -e system just to accomplish that
(which I have not, yet).
Please help.
Holly
--
gentoo-user@gentoo.org mailing list