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