[MacPorts] #30279: MPlayer @1.0rc4, Revision 1 fails with clang, llvm-gcc-4.2, Lion

MacPorts noreply at macports.org
Wed Oct 26 11:22:58 PDT 2011


#30279: MPlayer @1.0rc4, Revision 1 fails with clang, llvm-gcc-4.2, Lion
------------------------------------------+---------------------------------
  Reporter:  j_mach_wust@…                |       Owner:  macports-tickets@…                   
      Type:  defect                       |      Status:  closed                               
  Priority:  Normal                       |   Milestone:                                       
 Component:  ports                        |     Version:  1.9.2                                
Resolution:  fixed                        |    Keywords:  lion                                 
      Port:  MPlayer                      |  
------------------------------------------+---------------------------------

Comment(by dizzy@…):

 Ryan, thanks for the fix.

 As to what ecronin said, I don't have a strong opinion on this but I'll
 give my 2 cents (plus it's somewhat offtopic).

 When I saw the warning after the successful install I gave it a thought. I
 went with not bothering to install mplayer-devel instead because:
 - it's not clear to me that is supposed to be at least as stable as
 "mplayer", what if it's a snapshot of their SVN trunk or something like
 that (usually "-devel" packages are); the last thing I needed after not
 being able to compile it for months was to run into other issues because I
 would be running alpha grade code; related to this, what is the update
 policy of the "mplayer-devel" code, do they get in only minor code changes
 (minimal impact, like a stable release would have) or as I said it's a
 snapshot of their TRUNK and thus every time I run "port upgrade outdated"
 I risk breaking my "mplayer"? That is, even if "mplayer" wasn't meant as a
 stable release, just the fact that no updates are happening to it (other
 than small fixes like those introduced by the MacPorts folks) makes it so.
 - "mplayer" so far has worked very well for me and I don't have any bugs
 or lack of features that would make me interested in an alternative (and
 after all, the golden principle is "if it works, don't fix it"); however
 I, had no idea that mplayer-devel would have solved the compile issue,
 that would have been a good occasion to make the switch

-- 
Ticket URL: <https://trac.macports.org/ticket/30279#comment:25>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list