On 29 Oct 2018, at 23:07, Michael wrote:
So for what it's worth, after writing this out and going over what it
takes, I have ffmpeg finally working:
x264 @20171225_0 (active)
x265 @2.8_1 (active)
x265 @2.9_0
Something has to be out of date, and at least this is the least out of
date.
sh-3.2$ port installed ffmpeg
The following ports are currently installed:
ffmpeg @4.0.2_1+gpl2+x11 (active)
sh-3.2$ type ffmpeg
ffmpeg is /opt/local/bin/ffmpeg
sh-3.2$ otool -L /opt/local/bin/ffmpeg | grep libx2
/opt/local/lib/libx264.152.dylib (compatibility version 0.0.0, current
ve
I was compiling git as ppc64 on my G5 running Leopard 10.5.8, and it failed
when trying to configure the port in the subject. A quick search shows that
my exact failure mode seems to have been very common: while configuring
p5.26-locale-gettext, it complains that gettext isn't installed and
recomme
So for what it's worth, after writing this out and going over what it takes, I
have ffmpeg finally working:
x264 @20171225_0 (active)
x265 @2.8_1 (active)
x265 @2.9_0
Something has to be out of date, and at least this is the least out of date.
On 2018-10-29, at 7:47 PM, Ryan Schmidt wro
On 2018-10-29, at 7:47 PM, Ryan Schmidt wrote:
> On Oct 29, 2018, at 21:26, Michael wrote:
>
>> So two things when I attempted to update macports and ffmpeg.
>>
>> Number 1: There was a HUGE chain of things to update first. Surprising to me
>> was what looked like all of Xwindows.
>>
>> XWi
Is there a way to determine what's in an in-active port?
Attempting to ask "contents" does not work.
Here's what does *not* work:
bash-3.2# port installed x264
The following ports are currently installed:
x264 @20160119_0
x264 @20161201_0 (active)
x264 @20170522_0
x264 @20171225_0
bash-3.
On Oct 29, 2018, at 21:26, Michael wrote:
> So two things when I attempted to update macports and ffmpeg.
>
> Number 1: There was a HUGE chain of things to update first. Surprising to me
> was what looked like all of Xwindows.
>
> XWindows? Why?
>
> After X, it updated openssl, then sqlite3, t
So two things when I attempted to update macports and ffmpeg.
Number 1: There was a HUGE chain of things to update first. Surprising to me
was what looked like all of Xwindows.
XWindows? Why?
After X, it updated openssl, then sqlite3, then python select, then python,
then more of X ... followe
On 29 Oct 2018, at 16:35, Murray Eisenberg wrote:
That worked, thanks!
Would “source ~/.profile” also have accomplished the same end?
Only if your .profile sets the PATH environment variable, which most do.
However, it is quite possible that your .profile assumes that it is only
run once wh
That worked, thanks!
Would “source ~/.profile” also have accomplished the same end?
> On 29 Oct2018, at 4:26 PM, Rainer Müller wrote:
>
> On 2018-10-29 21:05, Murray Eisenberg wrote:
>> After
>>
>> sudo port select --set python python37
>>Selecting 'python37' for 'python' succeeded. 'pytho
On 2018-10-29 21:05, Murray Eisenberg wrote:
> After
>
> sudo port select --set python python37
> Selecting 'python37' for 'python' succeeded. 'python37' is now active.
> I have:
>
> port select --list python
> Available versions for python:
> none
> python27
> python27-apple
> pyt
After
sudo port select --set python python37
Selecting 'python37' for 'python' succeeded. 'python37' is now
active.
I have:
port select --list python
Available versions for python:
none
python27
python
12 matches
Mail list logo
