Trouble upgrading Macports to Sierra

2017-03-30 Thread Barrie Stott
I recently installed Sierra and am now coming to migrating my MacPorts ports using https://trac.macports.org/wiki/Migration. Steps 1 and 2 seemed ok but step 3 failed with the following information: gbs:macports $ port -qv installed > myports.txt Error: Current platform "darwin 16" does not

Re: Trouble upgrading Macports to Sierra

2017-03-30 Thread Barrie Stott
On 30 Mar 2017, at 16:38, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > Hi, > > On 30/03/17 16:32, Barrie Stott wrote: >> I recently installed Sierra and am now coming to migrating my MacPorts ports >> using https://trac.macports.org/wiki/Migration. Steps 1

Re: Difficulty in upgrading MacPorts from El Capitan to Sierra

2017-04-04 Thread Barrie Stott
> On 4 Apr 2017, at 12:02, db <iams...@gmail.com> wrote: > > On 4 Apr 2017, at 09:44, Barrie Stott <zen146...@zen.co.uk> wrote: >> 2. I would like to be able to take a requested port and find the tree of >> ports that would need to be inst

Re: Difficulty in upgrading MacPorts from El Capitan to Sierra

2017-04-04 Thread Barrie Stott
> On 4 Apr 2017, at 15:36, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Apr 4, 2017, at 02:44, Barrie Stott wrote: > >> I have some questions: >> >> 1. After loading Sierra I noticed that the m/c was slower. Looking at a file >> to disp

Is anyone successfully using lout on Sierra?

2017-08-11 Thread Barrie Stott
I don’t remember having a problem with the lout port until I moved to Sierra. Now all my ports are fine except lout. Barrie.

Re: Is anyone successfully using lout on Sierra?

2017-08-11 Thread Barrie Stott
> On 11 Aug 2017, at 09:50, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: > > indeed, without the full log cant tell what is wrong. > > Best, K Sorry about that. Here is the full log. Barrie. main.log Description: Binary data > On Aug 11, 2017

Re: Is anyone successfully using lout on Sierra?

2017-08-12 Thread Barrie Stott
> On 12 Aug 2017, at 16:48, Ken Cunningham > wrote: > > >> On Aug 11, 2017, at 7:05 PM, Ken Cunningham >> wrote: >> >> While this is getting sorted out properly... > > > See:

Re: Error installing bash on Sierra

2017-05-27 Thread Barrie Stott
On 27 May 2017, at 13:11, Ryan Schmidt wrote: > > Barrie, > > The error in your log says: > >> :error:install Failed to install bash: no destroot found at: >>

Re: Error installing bash on Sierra

2017-05-27 Thread Barrie Stott
On 27 May 2017, at 09:13, Dave Horsfall wrote: > > Does not /bin/bash come with the base system on your box? It does on > mine, and has for years. > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." Thanks for the reply and yes it does.

Re: Do I need +universal to be used when installing ports?

2017-05-01 Thread Barrie Stott
Many thanks to the 5 people who wrote in answer to my query about using +universal. Your contributions all pointed the same way so I am now fully convinced that I have NEVER needed i386 and will not be using +universal in the future. Your help has been invaluable and I’m very grateful. Barrie.

Re: Do I need +universal to be used when installing ports?

2017-04-29 Thread Barrie Stott
On 29 Apr 2017, at 16:13, Richard L. Hamilton wrote: > > In favor of getting rid of it, the pre-built binaries (much faster to install > or upgrade) aren't built +universal; so if you get rid of it, you'll often > get them. Some things aren't pre-built, so you won't always