ppc64 build failure - asm code - bswap

David Timms dtimms at iinet.net.au
Tue Sep 23 15:22:10 CEST 2008


Adrian Reber wrote:
> On Mon, Sep 22, 2008 at 12:36:11AM +1000, David Timms wrote:
>> So it seems that bswap might not suit ppc64 hardware. If that is the  
>> case then:
>> # ppc64 build does not seem to support asm opcode bswap
>> ExcludeArch: ppc64
>> would seem appropriate an appropriate addition to the .spec. Does that  
>> make sense ?
>>
>> Note that it did build OK on i386|x86_64|ppc. I would have imagined that  
>> ppc64 opcodes would be a superset of ppc, so there might be something  
>> else going on ?
> 
> The following is the your problem:
> 
> %ifarch ppc x86_64
> ASM_X86=0
> %else
> ASM_X86=1
> %endif
> 
> 
> You forgot to mention ppc64 in that list and ppc64 can just not handle
> intel assembler just like ppc. 
I don't have much experience with this sort of thing. Is x86_64 not able 
to do x86 assembler ?
Given this was a package import that I didn't create the gcube.spec 
initially, should the "ifarch ppc x86_64" have been "ppc ppc64" ?

> You can also see it in the compiler command line from ppc64 build. It
> contains "-DASM_X86".

Thanks, Adrian.


More information about the rpmfusion-developers mailing list