| 1 |
On 16/03/11 19:51, Mike Frysinger wrote: |
| 2 |
> On Wednesday, March 16, 2011 05:36:21 Tomáš Chvátal wrote: |
| 3 |
>> Dne 16.3.2011 07:48, justin napsal(a): |
| 4 |
>>> On 15/03/11 22:25, Tomáš Chvátal wrote: |
| 5 |
>>>> i am seriously hurt by $(use_enable amd64 64) |
| 6 |
>>> |
| 7 |
>>> Where is the problem? The purpose of the eclass is not to repeat the |
| 8 |
>>> same code 20 times. Why can't this be here? |
| 9 |
>> |
| 10 |
>> Problem is in amd64, what if we get to 64b mips OR ppc64 or any other |
| 11 |
>> non-32bit arch? |
| 12 |
> |
| 13 |
> or using the upcoming x32 ABI with KEYWORDS=amd64 ? |
| 14 |
> |
| 15 |
> if a package has a configure flag to control "64bitness", it is absolutely |
| 16 |
> broken. figure out what exactly the "64bitness" means (pointer size ? data |
| 17 |
> width ? assumptions about size of long ?) and replace it with a proper |
| 18 |
> configure time check. then the whole 64 configure flag can be thrown away. |
| 19 |
> -mike |
| 20 |
|
| 21 |
Hi guys, |
| 22 |
|
| 23 |
I need your help figure out how to handle the situation. |
| 24 |
|
| 25 |
sample code is here: http://tinyurl.com/6ezv9uw |
| 26 |
|
| 27 |
the configure adds -D__amd64__ to C(PP)FLAGS. |
| 28 |
|
| 29 |
To me it should be set this on 64bit. Do I interpret that right? |
| 30 |
|
| 31 |
How can I check for 64bitness during configure? |
| 32 |
|
| 33 |
Thanks for help justin |
Archives