[MPlayer-users] Building MPlayer Fails

[Ivan Kowalenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jun 16, 2006, at 00.41, Guillaume POIRIER wrote:

> Hi,
>
> On 6/16/06, Ivan Kowalenko <ivan.kowalenko at gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Jun 14, 2006, at 02.40, Guillaume POIRIER wrote:
>>
>> > Hi,
>> >
>> > On 6/14/06, Ivan Kowalenko <ivan.kowalenko at gmail.com> wrote:
>> >> On Jun 14, 2006, at 00.30, Guillaume POIRIER wrote:
>> >> I probably should have mentioned this earlier, but I'm  
>> attempting to
>> >> use GCC 3.4.6, as opposed to the Apple provided GCC 4.0.1.  
>> Don't know
>> >> if this is an issue, but it's probably worth mentioning.
>> >
>> > That could indeed be an issue. I don't know OSX enough to be  
>> sure, but
>> > I'd say that before experienting with exotic setups, you'd be  
>> better
>> > off trying with the defaults of your platform to confirm that it
>> > works.
>>
>> Figures. I had heard that GCC 3.4 produced code that was, generally,
>> better (faster, smaller) than that produced by GCC 4.0.1.
>
> Be carefull, I meant using Apple's GCC instead of a version of GCC
> which you have apparently compiled from sources.
>
> What's more, experienced OSX users told me was that apple's gcc is
> heavily patched therefore it's not reasonable to compare apple's 4.0
> gcc with the one you'd get from gcc.gnu.org.
> (so if gnu gcc 4.0 is worse at generating good code than 3.4, it may
> not be true for apple's)

Probably should have expected that. I guess this will ruin my goal of  
using distcc in more projects (as 4.0.1 isn't easy to find on a lot  
of Debian systems)

>
>
>> > Once it works, your can do some experiments.
>> [snip]
>> >
>> > No idea, besides the fact that it looks like a problem with the
>> > Altivec intrinsics. Better try with Apple's GCC (which is MUCH  
>> better
>> > with regards to intrinsics than FSF's gcc).
>> >
>> > Guillaume
>>
>> I'm now using Apple's GCC 4.0.1. Again, a compile error (yes, I made
>> clean, and reconfigured). Another error (It's like I have the
>> Dynamically Linked Libraries Of The Damned).
>>
>> $ make
[snip]
>> make: *** [mplayer] Error 1
>
> I don't know what this error means. Please make sure you have all dev
> headers installed. If you have not forced any flag in configure, you
> should have all the required headers, but one never knows...
>
>> Thank you for the help. By now, I'd have given up and waited a month
>> or two for a new version of MPlayer to come out on SVN.
>
> ahem... well, if you wait till the next release, I'm afraid that by
> the time next release is out, you'd be a grandpa or that you will have
> died of old age. ;-)

Well, I didn't mean *release* release, but rather, a later... build?  
check-out? Sub-version? I don't know what you'd call it under SVN.

> Ok, now, seriously, if you have hit a bug in MPlayer build system
> (quite possible), and other osx users are able to reproduce it, then
> we will have a chance to fix it, and everybody wins!! So don't give
> up!!

Yeah, but if that were true, we'd probably have heard something from  
the MPlayerOSX guys by now. I'm not about to give up, I usually just  
wait out problems. Time usually helps.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEklmI187keuSyQSQRAsgTAJ407l+ax7JBi0gAcQ0P6rzqTQYKTgCfUr5V
zmDWoUc1J2Zm26UnhUtz1IE=
=KrrP
-----END PGP SIGNATURE-----