[mythtv-users] system profiling / cpu usage revisited
Joseph A. Caputo
jcaputo1 at comcast.net
Fri Jun 20 12:21:26 EDT 2003
> -----Original Message-----
> From: mythtv-users-bounces at snowman.net
> [mailto:mythtv-users-bounces at snowman.net]On Behalf Of Brian Lalor
> Sent: Friday, June 20, 2003 8:05 AM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] system profiling / cpu usage revisited
>
>
> Isaac Richards wrote:
>
> >>b> The only things I changed were settings.pro to force -march=athlon-xp
> >>b> and the --cpu=athlon-xp option to configure.
> >>
> >> Well, that's your problem right there (and your latter message
> >>confirms it). "athlon-xp" is not a recognized cpu option for
> >>"configure" so I believe you compiled without MMX support and assembly
> >>language code for the critical parts of libavcodec (which does most of
> >>the work).
> >
> >
> > Yup -- and that would be why the RTJPEG stuff was fine, as it
> doesn't use
> > libavcodec. Good catch, there =)
>
> It *is* available in gcc; I figured they were in some way
> related... Maybe an
> error should pop up when you force configure to use an un-recognized CPU?
Actually, you shouldn't need to specify a CPU in ./configure unless you're
using a non-MMX capable CPU, or a non-x86 CPU like PowerPC. You can still
put your specific processor in settings.pro.
-JAC
More information about the mythtv-users
mailing list