Fwd: Re: Foolish

[Craig Treleaven]

Whoops, meant to send this to the list...

>Date: Thu, 18 Apr 2013 08:46:11 -0400
>To: James Linder <jam at tigger.ws>
>From: Craig Treleaven <ctreleaven at cogeco.ca>
>Subject: Re: Foolish
>Cc:
>Bcc:
>X-Attachments:
>
>At 7:57 PM +0800 4/18/13, James Linder wrote:
>>On 18/04/2013, at 7:23 PM, Craig Treleaven wrote:
>>
>>>  At 3:52 AM -0500 4/18/13, Ryan Schmidt wrote:
>>>>  On Apr 17, 2013, at 21:37, James Linder wrote:
>>>>
>>>>>  I allowed myself to be seduced by 'self upgrade' and 'upgrade 
>>>>>outdated' (I was installing git)
>>>>>  sooo
>>>>>  can the Maintainers of MythTV attend to the totally broken port please.
>>>>>
>>>>>  mythtv-core.25 @0.25.3-Fixes-20121025 (multimedia)
>>>>>
>>>>>  ...
>>>>>  :info:build make[2]: Nothing to be done for `first'.
>>>>>  :info:build make[2]: Leaving directory 
>>>>>`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv-core.25/mythtv-core.25/work/mythtv-117b611e/mythtv/libs/libmythui'
>>>>>  :info:build ld: warning: directory '-L/opt/local/lib -arch 
>>>>>x86_64 /System/Library/Frameworks 
>>>>>-Wl,-dynamic,-search_paths_first' following -F not found
>>>>>  :info:build ld: file not found: /opt/local/lib/libx264.119.dylib
>>>>>  :info:build collect2: ld returned 1 exit status
>>>>>  :info:build make[2]: *** [libmythupnp-0.25.0.25.0.dylib] Error 1
>>>>>  :info:build make[2]: Leaving directory 
>>>>>`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv-core.25/mythtv-core.25/work/mythtv-117b611e/mythtv/libs/libmythupnp'
>>>>>  :info:build make[1]: *** [sub-libmythupnp-make_default] Error 2
>>>>
>>>>  My suggestion to you was going to be precisely to selfupdate and 
>>>>upgrade outdated, because the current version of the 
>>>>mythtv-core.25 port is @0.25.3-Fixes-20121025_3 not 
>>>>@0.25.3-Fixes-20121025 and the x264 port currently provides 
>>>>libx264.129.dylib not libx264.119.dylib. Please try once more to 
>>>>run "sudo port selfupdate" and "sudo port clean outdated" and 
>>>>"sudo port upgrade outdated". If that didn't include 
>>>>mythtv-core.25, then "sudo port clean mythtv-core.25" and "sudo 
>>>>port install mythtv-core.25". It installs fine for me. If it 
>>>>still won't install for you, file a bug report.
>>>>
>>>>  http://guide.macports.org/chunked/project.html
>>>
>>>  James, would you please report back one way or the other?  I 
>>>haven't updated mythtv-core.25 on my own systems for some time as 
>>>I've been struggling trying to find a workable config for 0.26.
>>
>>Craig
>>just compound wossname:
>>
>>As per above, fails as ffmpeg is not compatablewith building myth
>>deactivate ffmpeg: can't do that transcode etc depend on it
>>uninstall transcode et al: cant do that you did not specify version
>>specifies version + deactivate: no output at all, but still active
>
>?? I think you're making this harder than it really is.  Myth comes 
>with its' own version of ffmpeg.  If the 'regular' MacPorts version 
>of ffmpeg is installed, the myth build process gets confused.  All 
>you have to do is deactivate ffmpeg while building myth and then 
>re-enable it later.
>
>To deactivate, when more than one version has been installed, you 
>have to specify the version.  Find out the versions with 'port 
>installed <portname>'.  I don't have ffmpeg installed, so let me use 
>npm as an example:
>
>$ port installed npm
>The following ports are currently installed:
>   npm @1.1.66_0
>   npm @1.2.2_0
>   npm @1.2.15_0 (active)
>
>If I wanted to deactivate npm, I would enter:
>
>$ sudo port deactivate npm @1.2.15_0
>
>After installing or upgrading the conflicting port (mythtv-core.25 
>in your case), the port can be made active again with:
>
>$ suo port activate npm @1.2.15_0
>
>These operations run very quickly.
>
>HTH
>
>Craig


-- 
--
Craig Treleaven, CA -- Clearview Consulting
(905) 829-2054  ctreleaven at cogeco.ca