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

> On Jul 29, 2016, at 1:35 AM, Ken Cunningham > wrote: > > Hi, > > There are many here smarter than me, but it would see your error is > here: > >> /opt/local/bin/clang++-mp-3.3 -pipe -Os -stdlib=libc++ -arch i386 >> -mmacosx-version-min=10.6

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

> On Jul 29, 2016, at 4:05 PM, Ken Cunningham > wrote: > > I believe macports automatically sets build_arch to the proper value > depending on your hardware . > >

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

> On Jul 29, 2016, at 10:57 AM, [ftp83plus] wrote: > > And why would it use clang-3.3 when it's explicitly told to use clang 3.4? The build failure is in libomp, which has the following compiler whitelist: # According to documentation builds with clang >= 3.3

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

> > I followed the instructions for full uninstall: > https://guide.macports.org/chunked/installing.macports.uninstalling.html That is infinitely better, and gets all the other bits and pieces that might cause trouble. > > this is the only occurence of "build_arch" in macports.conf, and is

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

Some more: El 2016-07-29, a las 11:56, Ken Cunningham escribió: > >> 2- correct the macports.conf to replace x86 by x86_64 architecture > > No, don't think so. My macports.conf has > > build_arch x86_64 > > near the top -- I installed macports two years ago. I can't recall at the >

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

Thanks Ken, this is the only occurence of "build_arch" in macports.conf, and is commented out, so shouldn't be taken into account: #build_arch i386 Comes from the most recent install of MacPorts. Should I replace it by build_archx86_64 ? El 2016-07-29, a las

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

> > Move your opt folder out of the way > > sudo mv /opt /opt-junked > Oh dear - this step is not quite right - I'm very sorry about that. There could be (and probably are) other things in your /opt folder that you don't want to move. If you did that, please move it back ( sudo mv

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

On 2016-07-29, at 7:57 AM, [ftp83plus] wrote: > SoI would have to 0- remove said files 1- reinstall MacPorts, Yes > 2- correct the macports.conf to replace x86 by x86_64 architecture No, don't think so. My macports.conf has build_arch x86_64 near the top -- I installed macports two

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

For the architectures, I have this in macports.conf: # CPU architecture to target. Supported values are "ppc", "ppc64", # "i386", and "x86_64". Defaults to: # - OS X 10.5 and earlier: "ppc" on PowerPC, otherwise "i386". # - OS X 10.6 and later: "x86_64" on Intel 64, otherwise "i386". #build_arch

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

It is acceptable for now, just annoyingly loud. SoI would have to 0- remove said files 1- reinstall MacPorts, 2- correct the macports.conf to replace x86 by x86_64 architecture But how would I know if the macports.conf contains the correct data? What should be the default for variants.conf?

Re: question about OpenSCAD 2015.03 on Snow Leopard, and a home-built libc++ package installer

On Jul 28, 2016, at 10:33 PM, Ken Cunningham wrote: > I would indeed have preferred to put libc++ and libc++abi into the app bundle > -- but all the other dylibs linked against them were hard-coded to look for > these two libraries in the /usr/lib directory. > > So I tried