Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Jeremy Huddleston Sequoia
> On Aug 1, 2016, at 4:05 PM, Ken Cunningham > wrote: > > Interestingly, I just went to update my libmacho and libunwind to the > universal variants given this conversation (already did the cxx and cxxabi > ports) -- but oddly, perhaps, this seemingly fully functional 10.6.8 /libc++ > system

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Ken Cunningham
Interestingly, I just went to update my libmacho and libunwind to the universal variants given this conversation (already did the cxx and cxxabi ports) -- but oddly, perhaps, this seemingly fully functional 10.6.8 /libc++ system with clang-3.8, all installed through macports, has neither libmach

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread [ftp83plus]
El 2016-08-01, a las 16:01, Jeremy Huddleston Sequoia escribió: > >> On Aug 1, 2016, at 11:55, [ftp83plus] wrote: >> >> >> El 2016-08-01, a las 02:49, Ryan Schmidt escribió: >> >>> On Aug 1, 2016, at 00:40, [ftp83plus] wrote: El 2016-07-31, a las 16:30, Ryan Schmidt escribió:

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Jeremy Huddleston Sequoia
> On Aug 1, 2016, at 11:55, [ftp83plus] wrote: > > > El 2016-08-01, a las 02:49, Ryan Schmidt escribió: > >> On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >>> >>> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: Could you also show us the CMakeOutput.log? >>> >>> Sure, here it is

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread [ftp83plus]
El 2016-08-01, a las 02:49, Ryan Schmidt escribió: > On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >> >> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: >>> >>> Could you also show us the CMakeOutput.log? >> >> Sure, here it is: >> CMakeOutput.log >> http://pastebin.com/XZ3WHA0F > > This ag

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Jeremy Huddleston Sequoia
> On Aug 1, 2016, at 01:58, Ryan Schmidt wrote: > > > On Aug 1, 2016, at 3:07 AM, Jeremy Huddleston Sequoia wrote: >> >> On Jul 31, 2016, at 23:49, Ryan Schmidt wrote: >>> >>> ld: warning: ignoring file /usr/lib/libc++.dylib, file was built for >>> unsupported file format ( 0xcf 0xfa 0xed 0x

Re: Holding a package at a given version

2016-08-01 Thread Daniel J. Luke
On Aug 1, 2016, at 11:44 AM, Adam Mercer wrote: > Sometimes I want to hold a given package at a specific version, is > there a way to do this with port? You need to set up a local repository where you can 'freeze' the port version at the one you want. [ideally you wouldn't have to do this ever,

Holding a package at a given version

2016-08-01 Thread Adam Mercer
Hi Sometimes I want to hold a given package at a specific version, is there a way to do this with port? Currently I use something like the following: $ sudo port upgrade outdated and not gnuplot however that only works if none of the outdated ports have a dependency on gnuplot. Is there somethi

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Ryan Schmidt
On Aug 1, 2016, at 3:07 AM, Jeremy Huddleston Sequoia wrote: > > On Jul 31, 2016, at 23:49, Ryan Schmidt wrote: >> >> ld: warning: ignoring file /usr/lib/libc++.dylib, file was built for >> unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 >> 0x 0 0x 0 0x 6 0x 0 0x 0

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Jeremy Huddleston Sequoia
> On Jul 31, 2016, at 23:49, Ryan Schmidt wrote: > > On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >> >> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: >>> >>> Could you also show us the CMakeOutput.log? >> >> Sure, here it is: >> CMakeOutput.log >> http://pastebin.com/XZ3WHA0F > > This a

Re: clang 3.4 can't be configured (part of a selfupdate)

2016-08-01 Thread Jeremy Huddleston Sequoia
> On Jul 31, 2016, at 23:44, Ryan Schmidt wrote: > > On Aug 1, 2016, at 00:44, Jeremy Huddleston Sequoia wrote: >> > >> On Jul 31, 2016, at 22:40, [ftp83plus] wrote: >>> >>> @Jeremy, I never explicitly selected clang-3.3, it is automatically >>> installed during Step 4 of >>> https://trac.m