[mythtv-users] Re: Problems using MythTV - errors with channel parameters

[Michael Obster]

Hi,

Gavin Hurlbut wrote:
> OK.  Your attitude smells like a cattle farm.   "What the hell is wrong with
> your software" my ass.   How about you learn to debug?  Oh, and to read the
> documentation.  I'm pretty sure the DVB stuff has been documented on the 
> mailing list if nowhere else.  If nothing else, you could tone down that
> attitude.
>

Thats pity that you react in this way. I talked with lots of people who 
had also problems like me. I think it's quite normal that you get such 
reactions when users are frustrated because they did read documentation, 
they did read many forums, they did try to get help from the mailing list.
But the problem still exists. This is not helpful.

> As for reading GCC Documentation, what about it?  Did you ever think that
> maybe... just maybe... the build environment might be optimizing for the
> specific platform you are compiling on?   Jeez.

Thats the point. There are many build kits out which do optimization for 
specific architectures. For example look at Gentoo or ROCK Linux. The 
build system optimizes the complete build environment for a selected 
cpu. The only exception on x86 is pentium 4, because this is still 
experimental *g*.
If you look at the assembler output ,gcc creates, there is much 
difference between the different platforms. For example parallel working 
on cpu registers, using SSE, using 3dnow or mmx and so on. Also a speed 
up is between this different optimization.
This features are in the gcc documentation for example ;-).
A hardcoded -march=pentiumpro does not recognizes such things, even I 
know qmake is a little bit tricky here. Personally I prefer autotools 
for building software.
So to get an optimal optimization, it is better to let the build 
determine which option is needed ;-).

> 
>>MythTV Version CVS from 2004-12-14
> maybe you should update this before spewing...  That's over a month old.
> 
I will try that, even that the problem should not be this version, 
because the maintainer of this package tests it on his platform before.
Only a database setup routine can be (because I don't think he is 
setting up his database from the beginning...)
I will report if it is working or not. Perhaps sending some patches :-).

>>gcc: 3.4.2
> And gcc 3.4.x has issues with a lot of code.  Maybe that's part of your
> problem too?
>

Not at all. It is working very well. The only big bug is in its lexer (I 
would fix it if I know how, but it is not trivil to fix :-( ). So some 
ANSI C will not compile :-(. But with some additional brackets the code 
works. And works better than 3.3.x or 3.2.x (sounds interesting...) :-).

>>Hoping for some help.
Still hoping. I will try a newer CVS from 2005-01-26 perhaps this solves 
the problem. I let me suprise ;-).

Cheers,
Michael Obster

P.S.: Please don't interpret every line as personal attack. That was not 
my intention. I only want to wake you up, because my and a lot of other 
peoples first impression of your software is not very good.
It is more for an article in the german Linux Magazin, how software 
should not be! No I will not write such one, because I don't know as 
much as I need for writing that for the moment.
I hope more if I write such an article in the future that you get some 
helpful development power to get your software much better than today 
;-). So it will be a more positive one ;-).