Dale wrote:
Here is a update. I been going back and forth with python-updater and
revdep-rebuild and it just never seems to finish cleanly. I think it
reached a stalemate. So, I'm doing a emerge -e world which will also
upgrade KDE.
Maybe this will get it going again.
Dale
:-) :-)
Dale wrote:
I already have --keep-going in make.conf. Good thought tho. Thing
is, it errors before it even starts. Complains about blockers and the
packages aren't even installed to block anything. Mostly KDE stuff too.
I'm running the script and will see what it does. Maybe it will
Well, this ain't good. Neither python-updater nor revdep-rebuild can
complete. Either it is a missing package or some other error. Am I to
the point where I have to reinstall?
If you can't sort out the mess manually, try emerge -e system, then
emerge -e world. You can also save some time by
On 05/06/2011 11:28 AM, Dale wrote:
Alan McKinnon wrote:
This is usually CFLAGS and other bits of env stuff. There's probably a
more
meaningful error earlier in the build log.
Can you post the full log for a failing file?
Here is one:
No, that's not it. It's this:
!!! Please attach the
Nikos Chantziaras wrote:
No, that's not it. It's this:
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.4/work/build-default/config.log
Hmmm. Thought it was the same. Here goes but it is lengthy:
root@smoker / # cat
On 06/05/11 11:08, Dale wrote:
That shed any light?
Dale
:-) :-)
Yes it does
/usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared
libraries: libmpfr.so.1: cannot open shared object file: No such file or
directory
you upgraded your mpfr. Now you have to
On 05/06/2011 12:08 PM, Dale wrote:
Nikos Chantziaras wrote:
No, that's not it. It's this:
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.4/work/build-default/config.log
Hmmm. Thought it was the same. Here goes but it is lengthy:
[...]
justin wrote:
On 06/05/11 11:08, Dale wrote:
That shed any light?
Dale
:-) :-)
Yes it does
/usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared
libraries: libmpfr.so.1: cannot open shared object file: No such file or
directory
you upgraded your mpfr. Now
Apparently, though unproven, at 11:15 on Friday 06 May 2011, justin did opine
thusly:
On 06/05/11 11:08, Dale wrote:
That shed any light?
Dale
:-) :-)
Yes it does
/usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared
libraries: libmpfr.so.1: cannot open
Dale wrote:
justin wrote:
On 06/05/11 11:08, Dale wrote:
That shed any light?
Dale
:-) :-)
Yes it does
/usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared
libraries: libmpfr.so.1: cannot open shared object file: No such file or
directory
you upgraded your mpfr.
Nikos Chantziaras wrote:
On 05/06/2011 12:08 PM, Dale wrote:
Nikos Chantziaras wrote:
No, that's not it. It's this:
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.4/work/build-default/config.log
Hmmm. Thought it was the same. Here goes
Alan McKinnon wrote:
Apparently, though unproven, at 11:15 on Friday 06 May 2011, justin did opine
thusly:
On 06/05/11 11:08, Dale wrote:
That shed any light?
Dale
:-) :-)
Yes it does
/usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared
libraries:
On Fri, 2011-05-06 at 12:18 +0200, Andrea Conti wrote:
AFAIK in order to avoid this kind of
breakage system ebuilds such as mpfr never delete old library
versions;
they just print a warning saying that the old library has been kept
around and should be manually deleted after running
/usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared
libraries: libmpfr.so.1: cannot open shared object file
Meaning, run revdep-rebuild :)
Yeah, right. So revdep-rebuild does its thing, finds out that gcc is
broken and tries to rebuild it with the broken gcc :)
In this
On 05/06/2011 12:45 AM, Dale wrote:
checking for i686-pc-linux-gnu-gcc... gcc
checking whether the C compiler works... no
I know you have it fixed now, but just thought I'd mention that
you will see the same error when compiling something in a directory
where you don't have write privileges.
Dale wrote:
On the list of things to do. Running python-updater now will run that
next.
Thanks.
Dale
:-) :-)
Well, this ain't good. Neither python-updater nor revdep-rebuild can
complete. Either it is a missing package or some other error. Am I to
the point where I have to
Albert Hopkins wrote:
On Fri, 2011-05-06 at 12:18 +0200, Andrea Conti wrote:
AFAIK in order to avoid this kind of
breakage system ebuilds such as mpfr never delete old library
versions;
they just print a warning saying that the old library has been kept
around and should be manually
Dale writes:
Dale wrote:
On the list of things to do. Running python-updater now will run that
next.
Well, this ain't good. Neither python-updater nor revdep-rebuild can
complete. Either it is a missing package or some other error. Am I to
the point where I have to reinstall?
Add
Alex Schuster wrote:
Dale writes:
Dale wrote:
On the list of things to do. Running python-updater now will run that
next.
Well, this ain't good. Neither python-updater nor revdep-rebuild can
complete. Either it is a missing package or some other error. Am I to
the
On 2011-05-06, Dale rdalek1...@gmail.com wrote:
P. S. One would think a Gentoo system could sit idle for a couple
months without this sort of mess.
It depends on which couple of months you happen to pick. ;)
Most of the time a couple months is OK. Once in a while there will
be several
20 matches
Mail list logo
