difficulties with MythTV on a MacMini1.1

[Jim Ham]

>> <snip>
>> The error in the log is:
>> 
>>> :info:build filter_yadif.c: In function 'filter_line_mmx2':
>>> :info:build filter_yadif.c:372: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'
>>> :info:build filter_yadif.c:380: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'
>>> :info:build filter_yadif.c:372: error: 'asm' operand has impossible constraints
>>> :info:build filter_yadif.c:372: error: 'asm' operand has impossible constraints
>>> :info:build filter_yadif.c:380: error: 'asm' operand has impossible constraints
>>> :info:build filter_yadif.c:380: error: 'asm' operand has impossible constraints
>>> :info:build make[2]: *** [filter_yadif.o] Error 1
>> 
>> It looks like this assembly-language code is not compatible with the processor in your Mac mini. Specifically it looks like the code is trying to use more processor registers than your processor has available. That's according to this page I found with a quick search:
>> 
>> http://stackoverflow.com/questions/8275859/error-cant-find-a-register-in-class-general-regs-while-reloading-asm
>> 
>> Only the first series of Intel Macs used the 32-bit Core processor; all the others use 64-bit processors, and 64-bit Intel processors have a lot more registers.
>> 
>> You should report this problem to the developers of mythtv so they can fix it.
>> 
>> A solution might be to tell mythtv to not use assembly code. I'm not sure what configure arguments might need to be added to do that.
> 
> Thanks for digging that up, Ryan.  I know there is a configure flag to not use Yasm--but I think these are in-line assembler commands. I'll have to check if/how to disable.
> 
> In case I need to, how does one check the specific processor model in the portfile?  Could you point me to some sample code?
> 
> Craig

Thanks for looking into this. I believe that my best bet for getting Myth to work on my mini is to put in the Core 2 Duo processor. Even if MythTV compiles performance may be an issue with the current 32 bit Core Duo.

FYI I get the same errors with Xcode 3.2.6  - no surprise.

Jim Ham
jimham at dslextreme.com