| 1 |
On Wednesday, March 16, 2011 05:36:21 Tomáš Chvátal wrote: |
| 2 |
> Dne 16.3.2011 07:48, justin napsal(a): |
| 3 |
> > On 15/03/11 22:25, Tomáš Chvátal wrote: |
| 4 |
> >> i am seriously hurt by $(use_enable amd64 64) |
| 5 |
> > |
| 6 |
> > Where is the problem? The purpose of the eclass is not to repeat the |
| 7 |
> > same code 20 times. Why can't this be here? |
| 8 |
> |
| 9 |
> Problem is in amd64, what if we get to 64b mips OR ppc64 or any other |
| 10 |
> non-32bit arch? |
| 11 |
|
| 12 |
or using the upcoming x32 ABI with KEYWORDS=amd64 ? |
| 13 |
|
| 14 |
if a package has a configure flag to control "64bitness", it is absolutely |
| 15 |
broken. figure out what exactly the "64bitness" means (pointer size ? data |
| 16 |
width ? assumptions about size of long ?) and replace it with a proper |
| 17 |
configure time check. then the whole 64 configure flag can be thrown away. |
| 18 |
-mike |
Archives