On 07/05/10 17:39:36, Arttu V. wrote:
> On 7/5/10, Helmut Jarausch <[email protected]> wrote:
> >
> > Hi,
> >
> > this errors baffles me.
> >
> > Emerging media-gfx/exact-image works just fine on one machine
> > but fails on a very similar (Gentoo) machine with
> > install: target `/var/tmp/portage/media-gfx/exact-image-0.8.1/
> image//
> > usr/lib64/python2.6/site-packages/' is not a directory: No such
> file
> or
> > directory
> >
> > Has anybody an idea where this strange install path might come
> from?
>
> Can you be more specific on the 'strangeness'? Which part looks odd?
>
> For a quick glimpse it would seem to be a regular temporary 'image'
> directory which is part of every package's install phase. Only once
> files have been successfully installed under this temporary 'image'
> (directory) will portage merge that directory's contents to
> respective
> real directories.
>
> As for the error itself, it could be a parallel make problem (goes
> temporarily away with MAKE_OPTS="-j1", but should still be reported
> at
> bugs.gentoo.org) or a lazy installer script which isn't properly
> creating the directories to which it will try to install files (which
> should also be reported at b.g.o, as it might be a gentoo-only
> problem).
>
> --
> Arttu V. -- Running Gentoo is like running with scissors
>
Thanks!
MAKEOPTS=-j1 didn't help
instead of
/var/tmp/portage/media-gfx/exact-image-0.8.1/image//usr/lib64/
python2.6/site-packages
there is a file
/var/tmp/portage/media-gfx/exact-image-0.8.1/image
/usr/lib/python2.5/site-packages
note lib not lib64
python2.5 not python2.6
eselect python list gives
Available Python interpreters:
[1] python2.6 *
[2] python3.1
So, where does this come from?
Many thanks for a hint,
Helmut.
