[Ffmpeg-cvslog] r5493 - in trunk/libavcodec/ppc: dsputil_altivec.c dsputil_h264_template_altivec.c

[Guillaume POIRIER]

Hi,

On 6/21/06, Luca Barbato <lu_zero at gentoo.org> wrote:
> Guillaume POIRIER wrote:
> > Hi,
> >
> > On 6/17/06, lu_zero <subversion at mplayerhq.hu> wrote:
> >
> > Looks like the following hunk broke compilation on OSX 10.3
> >
>
> Sigh, partially fixed it, could you please check again?

Yep, that part builds fine now.

What's more, I managed to make MPlayer build on OSX 10.3 following
what's explained here:
http://www.idevapps.com/forum/showthread.php?p=49361
Compilation/linking was broken for a long time, and I indend to
document how to overcome this problem for MPlayer. (I don't know if
it's worth spending some time to fix it though)


In short:

This problem is the result of Apple developers using 10.4 to compile
their software and distributing the binaries to 10.3 users via
Software Update. The undefined symbols are present in the 10.4
operating system, but not 10.3. The previous solution is to downgrade
to Quicktime 7.0.1. Here is a better solution.

Obtain an older copy of the frameworks. I've provided one at
(hopefully this doesn't violate my Software License Agreement):

http://rapidshare.de/files/20281171/CompatFrameworks.tgz.html


What you will get is a compressed file that contains the Quicktime
7.0.1 Framework and a 10.3.9 QuartzCore Framework. I don't know the
exact version of the QuartzCore Framework but it does work.

Uncompress the files somewhere that is not in your System folder. (ie.
do not install these Frameworks into your /System/Library/Frameworks!
They are only for getting around compiler errors!) For command-line
weenies you can use the following command in the Terminal application:

Code:

gunzip < CompatFrameworks.tgz | tar xvf -


in your Makefiles you should add:

Code:

-F/path/to/where/you/extracted


Or in X-Code you can just select these Frameworks instead of the System ones.

Your resulting binary/application will actually use the framework that
is installed on your system via dynamic links that are resolved at
run-time. (You can verify this using otool -l) I hope this helps.
Hopefully this will spare all the QT, SDL, Emacs, MPlayer, TCL,
Python, and SC developers and users a fair amount of grief.
Unfortunately this doesn't completely solve problems with
fink/opendarwin ports that attempt to automate the build process.

-- 
"Success consists of going from failure to failure without loss of enthusiasm."
 -- Winston Churchill