Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-alt
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-alt@g.o
From: Maurice Volaski <mvolaski@...>
Subject: Re: Re: [Q] What's causing python on Opensolaris to fail to import modules?
Date: Tue, 24 Jun 2008 14:06:08 -0400
Ooos, sorry just was I was formally submitting this weirdness as, 
http://bugs.gentoo.org/show_bug.cgi?id=229243, I realize the last 
part of your email, but it's still not clear why it causes a problem. 
If LDFLAGS is set, then why should gcc -m64 have trouble? In fact, it 
works OK when the 64-bit gcc library is moved to /usr/sfw/lib.



>On 23-06-2008 17:23:57 -0400, Maurice Volaski wrote:
>>>  I think I hit the same issue and I added a little note for it in the
>>>  bootstrap guide.  If you're bootstrapping 64-bits, you need to have the
>>>  64-bits paths in your searchpath, where they are non standard.
>>>
>>>  It's in this line:
>>>
>>>  If you are targetting a 64-bits native Prefix, append -L and -R flags
>>>  for /usr/sfw/lib/64 to your LDFLAGS. Additionally set CC="gcc -m64",
>>>  CXX="g++ -m64" and HOSTCC="gcc -m64".
>>>
>>>  note the /usr/sfw/lib/64, it contains the 64-bits version of
>>>  libgcc_s.so.1, that the linker should find (after skipping the
>>>  incompatible 32-bits version).
>>>
>>>  If you already did this, it looks like something weird is going on.
>>
>>  First, I assume the guide you mean is 
>>  http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml. 
>
>yes
>
>>  If so, though it's not the cause of the problem, but shouldn't those 
>>  variables be set before bootstrapping python?
>
>Well, if you refer to the ones "./bootstrap-prefix ...", then NO.  Those
>packages are build tools only (not libraries or stuff you're actually
>going to keep) and are just compiled 32-bits.  This saves you from a lot
>of trouble.  If you set -m64 before you did those, your python problems
>comes from there.
>
>>  Now, I had them set them when I bootstrapped python, so something weird
>>  is going on. I was able to get past it by moving the 32-bit libgcc out of
>>  the way and creating a symlink in /usr/sfw/lib to the 64-bit version and
>>  it seems to be working.
>
>Then you better remove everything, and restart from scratch again
>carefully following the guide.  The order of things is highly important!
>
>
>--
>Fabian Groffen
>Gentoo on a different level

-- 

Maurice Volaski, mvolaski@...
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
-- 
gentoo-alt@g.o mailing list


Replies:
Re: Re: Re: [Q] What's causing python on Opensolaris to fail to import modules?
-- Fabian Groffen
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: [Q] What's causing python on Opensolaris to fail to import modules?
Next by thread:
Re: Re: Re: [Q] What's causing python on Opensolaris to fail to import modules?
Previous by date:
Re: colorization errors with portage-2.2.00.10760
Next by date:
Re: Re: Re: [Q] What's causing python on Opensolaris to fail to import modules?


Updated Jun 17, 2009

Summary: Archive of the gentoo-alt mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.