Re: MacVim version

2016-08-29 Thread Richard L. Hamilton
> On Aug 29, 2016, at 11:20, David Evans wrote: > > On 8/29/16 7:38 AM, Richard L. Hamilton wrote: >> Running AppFresh (checks versions against iusethis database...not always >> accurate but better than nothing) told me that MacVim's web site, as of 27 >> August, has 7.4r107. Macports current

Re: MacVim version

2016-08-29 Thread David Evans
On 8/29/16 7:38 AM, Richard L. Hamilton wrote: > Running AppFresh (checks versions against iusethis database...not always > accurate but better than nothing) told me that MacVim's web site, as of 27 > August, has 7.4r107. Macports currently has 7.4r106. > > Naturally, I'm not going to grab an u

MacVim version

2016-08-29 Thread Richard L. Hamilton
Running AppFresh (checks versions against iusethis database...not always accurate but better than nothing) told me that MacVim's web site, as of 27 August, has 7.4r107. Macports currently has 7.4r106. Naturally, I'm not going to grab an update for a packaged version directly from elsewhere...a

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

2016-08-29 Thread Ken Cunningham
FYI - the gtk3 upgrade does ultimately proceed normally on 10.6, once the LibCxxOnOlderSystems toolchain is repaired, per the separate instructions I posted. The problem was not with gtk specifically, but the toolchain it appears. Ken $ sudo port upgrade gtk3 ---> Computing dependencies fo

LibCxx on older systems toolchain blew up on 10.6 -- and fixed -- WAS Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

2016-08-29 Thread Ken Cunningham
Thanks for the info. I realize it's a small audience, and I'm happy to help, and in fact, don't mind plugging away at it when I have some time. No wonder the OP had trouble though. The toolchain blew up with the last updates to cctools and ld64, and the current instructions and state of things d

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

2016-08-29 Thread Mojca Miklavec
On 28 August 2016 at 23:21, Ken Cunningham wrote: > OK - I see what happened. > > All traces of llvm37 have been from the new ld64 portfile. > > and so when the porfile saw my requested +llvm37, it saw that as no llvm > variant, and defaulted to llvm34. And now my toolchain is looking pretty > in

Re: [KDE/Mac] another round of KF5 test-building please

2016-08-29 Thread René J . V . Bertin
On Thursday July 07 2016 14:29:15 Kurt Hindenburg wrote: Hello Kurt, I was under the impression I'd already replied to this mail of yours, but cannot find any trace of that, so here goes again. >Hi, first off, I want to thank you for doing all this work getting KF5 to work >on Mac OS X. You'r