[MPlayer-dev-eng] [PATCH] MacOS X build weirdness

[Chris Roccati]

On 24 Apr 2006, at 13:52 , Jan Paul Schmidt wrote:

> This does not look like the complete output to me. If compilation  
> really
> fails during linking, you should use

The complete output of make?
That would be PAGES long...

> before compiling, so no old files lay around. Or try a new clean
> checkout from CVS.

The error appears building from a clean and complete checkout.

> If compilation does not fail, it is one of this linker warning you can
> ignore.

It is not a warning. It is an ERROR.
>> This seems to be due to the fact that the default MPlayer binary
>> tries to be both a Quartz application AND a X11 application - if this
>> actualy makes any sense is left as an exercise for the reader...
> How should MPlayer know, you don't want X11? Quartz does not imply no
> X11 for me. But yes, it probably only makes sense for a developer to
> compare output systems.

As I said, that's what happens when you do a default ./configure.
I don't claim it is right or wrong. It simply does not build  
(although I don't really care about X11).

>> I don't recall this happening before (but I built MPlayer from CVS  
>> last
>> time in november); by manually disabling X11, obviously, everything
>> builds fine.
> Things have changed since November ;o)

That's why I checked out the latest CVS.