| 1 |
Ooos, sorry just was I was formally submitting this weirdness as, |
| 2 |
http://bugs.gentoo.org/show_bug.cgi?id=229243, I realize the last |
| 3 |
part of your email, but it's still not clear why it causes a problem. |
| 4 |
If LDFLAGS is set, then why should gcc -m64 have trouble? In fact, it |
| 5 |
works OK when the 64-bit gcc library is moved to /usr/sfw/lib. |
| 6 |
|
| 7 |
|
| 8 |
|
| 9 |
>On 23-06-2008 17:23:57 -0400, Maurice Volaski wrote: |
| 10 |
>>> I think I hit the same issue and I added a little note for it in the |
| 11 |
>>> bootstrap guide. If you're bootstrapping 64-bits, you need to have the |
| 12 |
>>> 64-bits paths in your searchpath, where they are non standard. |
| 13 |
>>> |
| 14 |
>>> It's in this line: |
| 15 |
>>> |
| 16 |
>>> If you are targetting a 64-bits native Prefix, append -L and -R flags |
| 17 |
>>> for /usr/sfw/lib/64 to your LDFLAGS. Additionally set CC="gcc -m64", |
| 18 |
>>> CXX="g++ -m64" and HOSTCC="gcc -m64". |
| 19 |
>>> |
| 20 |
>>> note the /usr/sfw/lib/64, it contains the 64-bits version of |
| 21 |
>>> libgcc_s.so.1, that the linker should find (after skipping the |
| 22 |
>>> incompatible 32-bits version). |
| 23 |
>>> |
| 24 |
>>> If you already did this, it looks like something weird is going on. |
| 25 |
>> |
| 26 |
>> First, I assume the guide you mean is |
| 27 |
>> http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml. |
| 28 |
> |
| 29 |
>yes |
| 30 |
> |
| 31 |
>> If so, though it's not the cause of the problem, but shouldn't those |
| 32 |
>> variables be set before bootstrapping python? |
| 33 |
> |
| 34 |
>Well, if you refer to the ones "./bootstrap-prefix ...", then NO. Those |
| 35 |
>packages are build tools only (not libraries or stuff you're actually |
| 36 |
>going to keep) and are just compiled 32-bits. This saves you from a lot |
| 37 |
>of trouble. If you set -m64 before you did those, your python problems |
| 38 |
>comes from there. |
| 39 |
> |
| 40 |
>> Now, I had them set them when I bootstrapped python, so something weird |
| 41 |
>> is going on. I was able to get past it by moving the 32-bit libgcc out of |
| 42 |
>> the way and creating a symlink in /usr/sfw/lib to the 64-bit version and |
| 43 |
>> it seems to be working. |
| 44 |
> |
| 45 |
>Then you better remove everything, and restart from scratch again |
| 46 |
>carefully following the guide. The order of things is highly important! |
| 47 |
> |
| 48 |
> |
| 49 |
>-- |
| 50 |
>Fabian Groffen |
| 51 |
>Gentoo on a different level |
| 52 |
|
| 53 |
-- |
| 54 |
|
| 55 |
Maurice Volaski, mvolaski@××××××××.edu |
| 56 |
Computing Support, Rose F. Kennedy Center |
| 57 |
Albert Einstein College of Medicine of Yeshiva University |
| 58 |
-- |
| 59 |
gentoo-alt@l.g.o mailing list |
Archives