From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Sat, 26 Mar 2011 21:12:08 +0000 [thread overview]
Message-ID: <201103262112.28206.michaelkintzios@gmail.com> (raw)
In-Reply-To: <AANLkTinbo9qv=4o6x-tcWSPqhxPrX_R9yQAEMM2_yBWg@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 2142 bytes --]
On Saturday 26 March 2011 20:53:50 Mark Knecht wrote:
> On Sat, Mar 26, 2011 at 1:36 PM, Bill Longman <bill.longman@gmail.com>
wrote:
> > On Sat, Mar 26, 2011 at 12:56 PM, Mark Knecht <markknecht@gmail.com>
wrote:
> <SNIP>
>
> >> I had nothing linked to libmpfr.so.1 so that wasn't the root cause/
> >>
> >> In my case it seems to be driven by bugs like this:
> >>
> >> http://bugs.gentoo.org/show_bug.cgi?id=360425
> >>
> >> Seems the only thing to do it just wait for devs to fix it. (And
> >> wonder why something like python-2.7 gets released as stable with
> >> stuff like this hanging about....)
> >>
> >> Cheers,
> >> Mark
> >
> > The libmpfr change bit me on one of my amd64 machines. I did the
> > revdep-rebuild on the library and then gcc was broken. I recompiled
> > everything but still sandbox and gcc won't compile.
> > --
> > Bill Longman
>
> Bill,
> I got bit by the sandbox/gcc problem yesterday. In my case, on a
> machine with a KDE profile && after reviewing Gentoo bug reports, I
> did the following:
>
> eselect profile set 1
> cd /lib
> ln -s ../lib32/ld-linux.so.2 .
> emerge sandbox
> emerge --sync
> emerge glibc
> emerge @preserved-rebuild
> eselect profile set 4
> emerge -e -j9 @system
>
> and an hour later I was back to functional without those messages
> about not being able to build C programs, etc.
>
> I don't suggest ANY of that is understood by the likes of me but it
> did seem to solve the problem which was (apparently) wrapped around
> some sort of missing link which allows 64-bit machines to run 32-bit
> programs. (Or that's about all I could get out of what I read....)
>
> Hope this helps, and hoping someone more knowledgable than I chimes in
> with what I should have/could have done to do this more easily.
>
> Cheers,
> Mark
I had a problem with it too (gcc would not compile) but that was because I was
trying to emerge everything at the same time. I slowed down, finished with
the libmpfr revdep-rebuild and then run python updater, switched to python-2.7
and run revdep-rebuild again.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-26 21:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 0:11 [gentoo-user] python-2.7 && python-updater Mark Knecht
2011-03-25 0:28 ` Dale
2011-03-25 3:42 ` Amankwah
2011-03-25 4:48 ` Paul Hartman
2011-03-25 9:37 ` Dale
2011-03-25 9:50 ` Neil Bothwick
2011-03-25 13:56 ` Mark Knecht
2011-03-25 14:26 ` Neil Bothwick
2011-03-25 18:14 ` [gentoo-user] humor: " James
2011-03-25 14:33 ` [gentoo-user] " Roman Zilka
2011-03-25 16:44 ` Dale
2011-03-25 14:33 ` Paul Hartman
2011-03-25 16:46 ` Dale
2011-03-28 13:22 ` KH
2011-03-28 15:02 ` Mark Knecht
2011-03-28 15:41 ` Roman Zilka
2011-03-29 8:26 ` KH
2011-03-25 13:02 ` [gentoo-user] " Simon Siemonsma
2011-03-25 16:50 ` Dale
2011-03-25 19:09 ` [gentoo-user] " Stéphane Guedon
2011-03-25 19:21 ` Grant
2011-03-25 20:38 ` Neil Bothwick
2011-03-26 19:10 ` Mark Knecht
2011-03-26 19:22 ` Mick
2011-03-26 19:56 ` Mark Knecht
2011-03-26 20:36 ` Bill Longman
2011-03-26 20:53 ` Mark Knecht
2011-03-26 21:12 ` Mick [this message]
2011-03-26 21:16 ` Neil Bothwick
2011-03-26 21:33 ` Mark Knecht
2011-03-26 23:06 ` Adam Carter
2011-03-27 0:44 ` Neil Bothwick
2011-03-27 15:26 ` Mark Knecht
2011-03-27 15:47 ` Jacques Montier
2011-03-27 19:25 ` Neil Bothwick
2011-03-27 19:50 ` Mark Knecht
2011-03-27 20:05 ` Neil Bothwick
2011-03-28 0:45 ` Adam Carter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201103262112.28206.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox