On Sat, May 3, 2014 at 1:27 PM, Bill Christensen
billc_li...@greenbuilder.com wrote:
I installed a non-MacPorts package on my server the other day - WordPress
command line interface (wp-cli) which uses the wp command. It's working
properly.
But I just went to do my regular updates using
On May 03 12:27:18, billc_li...@greenbuilder.com wrote:
I installed a non-MacPorts package on my server the other day -
WordPress command line interface (wp-cli) which uses the wp
command. It's working properly.
But I just went to do my regular updates using MacPorts, and I've
lost my port
On 5/3/14 2:49 PM, Jan Stary wrote:
On May 03 12:27:18, billc_li...@greenbuilder.com wrote:
I installed a non-MacPorts package on my server the other day -
WordPress command line interface (wp-cli) which uses the wp
command. It's working properly.
But I just went to do my regular updates
Hello MP list,
I ran a sudo port upgrade outdated on my system as part of routine maintenance,
but found that clang 3.3 couldn't be rebuilt. In the log, I found error:
:info:build make[3]: ***
On May 3, 2014, at 18:29, semaphor...@yahoo.com wrote:
I ran a sudo port upgrade outdated on my system as part of routine
maintenance, but found that clang 3.3 couldn't be rebuilt. In the log, I
found error:
:info:build make[3]: ***
On May 3, 2014, at 16:11, Bill Christensen billc_li...@greenbuilder.com wrote:
The parallel machine shows:
/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
Are the repeats in that unneeded? I'm seeing several
