mythtv-core.26 build fails on x86_32/osx/10.6

[air_drummer@…]

libswscale/x86/rgb2rgb_template.c:814: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’

this seems to be the same problem as #20938:

ffmpeg/ffmpeg-devel fails to build on 10.6

and has been fixed...see

​http://mac-os-forge.2317878.n4.nabble.com/MacPorts-20938-ffmpeg-0-5-3-fails-to-build-on-10-6-td89473.html

"Just a note about the original build failure: this is a known problem when using gcc >= 4.2 and PIC on 32-bit x86. The possible solutions are either to not use PIC on x86 32-bit (--extra-cflags=-mdynamic-no-pic, or --disable-shared if you're anal about following shared lib recommendations/Apple broke the linker again), or use gcc 4.0 for ffmpeg/x86_32."

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log file of the build failure.

[ctreleaven (Craig Treleaven)]

Could you please clean, re-run and attach a full log. I'd like to see the output from configure which was performed prior to the above run.

[air_drummer@…]

here ya go...thanx 4 looking @ it:-)

[air_drummer@…]

/opt/local/bin/port install mythtv-core.26

[ctreleaven (Craig Treleaven)]

Are you looking to run only the frontend on this machine? (It is pretty underpowered to be a combined frontend/backend.) If so, you may want to look at the official packaged app. I believe JYA offers 32/64 universal bullds at:

​http://www.avenard.org/files/mythtv/mac/

I will look more at this issue but I feel that the time spent supporting 32bit Intel may be out of proportion to the number of users. If someone else wants to jump in and provide patches, that would be great.

[air_drummer@…]

just the frontend, running the backend on a linux box...thanx 4 the link, i'll give it a try.

and i would like 2 take a crack @ patching it...where do i sign up?-)

[air_drummer@…]

the MythFrontend-v0.26.0-175-g7f71e02 suffers the same defect as the macports release: the mfe starts the mythlogserver, which immediately crashes, latherrinserepeat:-P workaround is to start the 2 from the command line

[ctreleaven (Craig Treleaven)]

With MacPorts, use the Applescript helper (/Applications/MacPorts/MythTV/Mythfrontend.app etc) to start the app and it will start mythlogserver beforehand.

The official packaged app has never produced logs so they don't consider the mythlogserver crashes a problem(!).

[air_drummer@…]

no, it's the logserver started by the fe.app that crashes over&over:-P if i start the logger from the c/l b4 the fe.app, no problem...and the avenard app doesn't even run on 10.6.8 (see attached)

[air_drummer@…]

f-e doesn't run on 10.6.8

[air_drummer@…]

btw, the app does run on my 10.7 macbook pro (when i manually start the logserver) but playback is choppy...xbmc w/the myth plugin is smooth, and it runs nicely on the 10.6 minimac...jus'sayin';-)

[ctreleaven (Craig Treleaven)]

What are you saying? Is the official packaged app choppy or the MacPorts binary? If the official app, you need to seek support on the mythtv-users mailing list. (I think there are a couple of builds for 0.26--maybe you need to try the other.) If MacPorts, you need to open a new ticket.

[ctreleaven (Craig Treleaven)]

The good news: I was able to build mythtv-core.26 on a Core Duo Mini by adding --disable-asm and --mem-align-hack to the configure args. The BAD news is that without asm, it can barely keep up with 1080 interlaced material (using the most basic de-interlacer). Drops frames regularly, some audio glitches. 720P material is slightly better. The Myth ports on MacPorts are geared to providing frontend AND backend services and trying to run both would be an exercise in frustration. The bottom line is that 0.26 on these older 32 bit machines is just not worth it. Sorry.

Could a committer please close this ticket? Thanks.

[air_drummer@…]

thanx, i'll give it a try...but what's the problem w/just adding those config args? u've already done the work fcol;-\

as i only want to run the frontend on the minimac (better scheduling support than xbmc's...and can someone tell them 2 change "timer" to "schedule"?-) i can live w/non-deinterlaced;-)