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
> 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!
Gentoo on a different level
firstname.lastname@example.org mailing list