| 1 |
Nikos Chantziaras wrote: |
| 2 |
> Helmut Jarausch wrote: |
| 3 |
>> On 13 Feb, Nikos Chantziaras wrote: |
| 4 |
>>> Helmut Jarausch wrote: |
| 5 |
>>>> Hi, |
| 6 |
>>>> |
| 7 |
>>>> I'm working on an AMD opteron, definitely an AMD64 machine. |
| 8 |
>>>> |
| 9 |
>>>> /etc/make.conf contains |
| 10 |
>>>> CHOST="x86_64-pc-linux-gnu" |
| 11 |
>>>> |
| 12 |
>>>> my profile is |
| 13 |
>>>> default/linux/amd64/2008.0/desktop |
| 14 |
>>>> |
| 15 |
>>>> Still, when emerging sci-libs/acml, portage |
| 16 |
>>>> fetches the 32-bit variant of the package. |
| 17 |
>>>> The SRC_URI depends on use flags x86 and amd86. |
| 18 |
>>> This package is fetch restricted. It shouldn't actually fetch |
| 19 |
>>> anything. You have to download the correct tarball and place it in |
| 20 |
>>> /usr/portage/distfiles. |
| 21 |
>>> |
| 22 |
>> |
| 23 |
>> OK, my wording was wrong. I did fetch the 64-bit version but emerge |
| 24 |
>> didn't use it, but told me to fetch the 32-bit version. |
| 25 |
> |
| 26 |
> Hmm. Get that one too then and see which one is picked when the actual |
| 27 |
> emerge starts. It could be that it needs both. If it ends up building |
| 28 |
> the 32-bit one only, then I guess it's time for a bug report :) |
| 29 |
> |
| 30 |
> |
| 31 |
|
| 32 |
Its definitely a 64/32 bit problem and nothing to do with the int64 use |
| 33 |
flag? |
Archives