[mythtv-users] configure did not detect my cpu

[R. G. Newbury]

Fred McClain wrote:
> Yan Seiner wrote:
>> R. G. Newbury napsal(a):
>>   
>>> Fred McClain wrote:
>>>   
>>>     
>>>> Hello,
>>>> I'm trying to build mythtv. I got sources from:
>>>>
>>>> svn co http://svn.mythtv.org/svn/branches/release-0-20-fixes/mythtv
>>>>
>>>> I issued this configure command:
>>>>
>>>> ./configure --enable-dvb --enable-xvmc --enable-opengl-vsync \
>>>> --enable-xvmc-pro --enable-proc-opt --prefix=/usr
>>>>
>>>> And received this output:
>>>>
>>>> *** WARNING ***
>>>> Your CPU was not detected properly:
>>>>   uname -m: i686
>>>>   uname -p: unknown
>>>> model name: Intel(R) Core(TM)2 CPU      6400 @ 2.13GHz
>>>> ...
>>>>
>>>>
>>>> *Then when I run 'make' I get 'segmentation fault'. Do you think the 'segmentation fault' is related to uname not detecting processor correctly?
>>>>     
>>>>       
>>> I would not think that seg fault would be caused by that, but there have 
>>> been some problems reported here concerning problems with the 'arch' and 
>>> 'proc-opt' switches. Try it after deleting the '--enable-proc-opt' 
>>> switch. Configure seems to get a little confused.
>>>
>>> No promises however. Please report back....since I don't get that 
>>> problem on my Asus P5l-MX mb with Intell 6600 Core2Duo @ 2.4GHz....weird 
>>> that you do. Both uname -m and uname -p give my i686....
>>>   
>>>     
>> Worked for me with that CPU....
>>
>> ./configure --enable-xvmc --enable-opengl-vsync --enable-dvb 
>> --compile-type=debug --enable-proc-opt
>>
>> processor       : 1
>> vendor_id       : GenuineIntel
>> cpu family      : 6
>> model           : 15
>> model name      : Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz
>> stepping        : 6
>> cpu MHz         : 1600.164
>> cache size      : 2048 KB
>>
>> --Yan
>>
>>   
> config is now detecting my hardware. uname -m -> i686 uname -p unknown.
> 
> I now believe the Segmentation Fault is a memory problem and the memory 
> problem was causing configure to generate errors.
> many thanks,
> fred

Still something weird going on, since uname -p should return i686.....


Geoff