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

Hey Pat, FYI, I just finished wiping my SL VM and going through the motions yesterday. clang-3.8 seems to have some issues on the older versions of OS X, so I've updated the page to recommend staying at 3.7 for now. I suggest you edit macports.conf and just remove macports-clang-3.8 from the

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

> On Aug 4, 2016, at 10:23, [ftp83plus] wrote: > > Thanks to all, it seems to have worked so far until Step 8. I noticed Step 9 > disappeared in the page refresh. Was it unnecessary? It was made obsolete by libcxx becoming +universal by default, so there was no need to

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

Thanks to all, it seems to have worked so far until Step 8. I noticed Step 9 disappeared in the page refresh. Was it unnecessary? Pat El 2016-08-04, a las 00:00, Jeremy Huddleston Sequoia escribió: > Ah. Reordered. > > Do this first to pick up the +llvm38 variants of cctools and ld64: > >

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

Ah. Reordered. Do this first to pick up the +llvm38 variants of cctools and ld64: sudo port -v -n upgrade --enforce-variants cctools -llvm34 sudo port -v upgrade --enforce-variants ld64 -llvm34 > On Aug 3, 2016, at 20:16, [ftp83plus] wrote: > > Thanks, > > that

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

Thanks, that worked, partly. Now, on Step 7, I get: http://pastebin.com/dNRW6g2c How to solve it? El 2016-08-03, a las 12:09, Jeremy Huddleston Sequoia escribió: > >> On Aug 3, 2016, at 07:36, [ftp83plus] wrote: >> >> Hmmm, and how would I install the +universal

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

Pat, I seemed to have none of these issues... but I installed libomp-universal on my x86_64 compatible mac. libomp @3.8.1_0-universal (active) platform='darwin 10' archs='x86_64' And so it remains. That seems to have been the main reason I didn't run into any of the issues you have run

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

> On Aug 3, 2016, at 07:36, [ftp83plus] wrote: > > Hmmm, and how would I install the +universal variant of libcxx wile avoiding > the python-related bug? sudo port -v -f uninstall libcxxabi libcxx sudo port -v -s install libcxx > > PAt > > El 2016-08-01, a las 22:13,

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

> On Aug 3, 2016, at 9:36 AM, [ftp83plus] wrote: > > Hmmm, and how would I install the +universal variant of libcxx wile avoiding > the python-related bug? Use the +readline variant. ___ macports-users mailing list

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

Hmmm, and how would I install the +universal variant of libcxx wile avoiding the python-related bug? PAt El 2016-08-01, a las 22:13, Jeremy Huddleston Sequoia escribió: > >> On Aug 1, 2016, at 4:05 PM, Ken Cunningham >> wrote: >> >> Interestingly, I just

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

> 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

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

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

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

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

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

> 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?

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

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

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

> 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

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

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)

> 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 >>

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

> 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

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

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 again shows: ld: warning: ignoring file /usr/lib/libc++.dylib, file

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

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.macports.org/wiki/LibcxxOnOlderSystems. It is a dependency of

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

> On Jul 31, 2016, at 22:40, [ftp83plus] wrote: > > > El 2016-07-31, a las 16:30, Ryan Schmidt escribió: > >> On Jul 31, 2016, at 14:01, [ftp83plus] wrote: >> >>> libomp still fails to build as a dependency of clang 3.8 installation as >>> shown in Step 4: >>> >>>

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

El 2016-07-31, a las 16:30, Ryan Schmidt escribió: > On Jul 31, 2016, at 14:01, [ftp83plus] wrote: > >> libomp still fails to build as a dependency of clang 3.8 installation as >> shown in Step 4: >> >> main.log from >>

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

And why is the macports user's home directory not present: • :info:configure 2016-07-31 04:52:55.132 sw_vers[18075:903] CFPreferences: user home directory at file://localhost/opt/local/var/macports/home/ is unavailable. User domains will be volatile. Did you delete it, or was it never

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

> On Jul 31, 2016, at 13:30, Ryan Schmidt wrote: > > On Jul 31, 2016, at 14:01, [ftp83plus] wrote: > >> libomp still fails to build as a dependency of clang 3.8 installation as >> shown in Step 4: >> >> main.log from >>

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

On Jul 31, 2016, at 14:01, [ftp83plus] wrote: > > libomp still fails to build as a dependency of clang 3.8 installation as > shown in Step 4: > > main.log from > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/ >

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

Hello all, libomp still fails to build as a dependency of clang 3.8 installation as shown in Step 4: main.log from /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/ http://pastebin.com/9YwFQusZ This is earlier than Step

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

> On Jul 30, 2016, at 11:20 PM, Jeremy Huddleston Sequoia > wrote: > > >> On Jul 30, 2016, at 18:16, Ryan Schmidt wrote: >> >> >>> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: >>> El 29 jul 2016, a las 16:45, Lawrence Velázquez

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

> On Jul 30, 2016, at 18:16, Ryan Schmidt wrote: > > >> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: >> >>> El 29 jul 2016, a las 16:45, Lawrence Velázquez escribió: >>> On Jul 29, 2016, at 1:35 AM, Ken Cunningham wrote: >

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

Maybe, indeed. I just realized my package installer (and my OpenSCAD application) are x86_64 specific. And some 10.6.8 systems can't run that. I have a lot to learn. Ken On 2016-07-30, at 6:16 PM, Ryan Schmidt wrote: > >> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: >> >>> El 29 jul

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

> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: > >> El 29 jul 2016, a las 16:45, Lawrence Velázquez escribió: >> >>> On Jul 29, 2016, at 1:35 AM, Ken Cunningham wrote: >>> /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 30, 2016, at 7:24 PM, [ftp83plus] wrote: > > Should I simply let step 2 as it was, not > sudo port -v install libcxx +universal > > but > > sudo port -v install libcxx > > like I did when it failed the first time? I doubt that has anything to do with the

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

Should I simply let step 2 as it was, not sudo port -v install libcxx +universal but sudo port -v install libcxx like I did when it failed the first time? Thanks, Pat El 2016-07-30, a las 18:01, Lawrence Velázquez escribió: > On Jul 30, 2016, at 1:57 PM, [ftp83plus]

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

On Jul 30, 2016, at 1:57 PM, [ftp83plus] wrote: > Python 27 fails to build: http://pastebin.com/zJZM4vM8 and log: > http://pastebin.com/0L1rTQZP > > What is the issue this time? https://trac.macports.org/ticket/51891 vq ___

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

Thanks Lawrence, so I did: Step 1: OK as per https://guide.macports.org/chunked/installing.macports.uninstalling.html Step 2: MODIFIED: sudo port -v install libcxx +universal Python 27 fails to build: http://pastebin.com/zJZM4vM8 and log: http://pastebin.com/0L1rTQZP What is the issue this

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

On Jul 30, 2016, at 8:58 AM, [ftp83plus] wrote: > So should I rebuild libcxx +universal variant first before performing > Step 4 of the LibcxxOnOlderSystems? Yes, unless you can figure out why libomp is being installed +universal and prevent that. vq

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

> El 29 jul 2016, a las 16:45, Lawrence Velázquez > escribió: > >> On Jul 29, 2016, at 1:35 AM, Ken Cunningham >> > >> wrote: >> >> Hi, >> >> There are many here smarter than me, but it would see

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: clang 3.4 can't be configured (part of a selfupdate)

Oh - it's arch x86_64, by the way... late night brain fart.] More I look at the different issues you have going on here, more I think what I would do is just start over. It's time consuming, but 100% reliable. I'd delete these three files: -rwxr-xr-x 1 root wheel 1186580 12 Jan 2016

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

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 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names

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

Thanks Ken, I am currently attempting the Install Libcxx on Older Systems procedure as it was how you solved it. However, it fails at step 4 after hours trying to compile: > -- Configuring incomplete, errors occurred! > See also >

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

The following ports are currently installed: cctools @877.5_2+llvm37 cctools @877.8_0+llvm37 cctools @886_1+llvm37 (active) ld64 @2_0+ld64_136 (active) ld64-136 @136_4+llvm37 (active) El 2016-07-27, a las 22:40, Mihai Moldovan escribió: > On 26.07.2016 02:13 PM, [ftp83plus] wrote: >>

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

On 26.07.2016 02:13 PM, [ftp83plus] wrote: > I am currently attempting a "port selfupdate" operation before installing two > ports I'd like to test. > > However, it fails for a reason I don't understand: > [...] Also interesting might be the output of `port installed 'ld64*' cctools` This

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

> On Jul 26, 2016, at 19:58, Ryan Schmidt wrote: > > > On Jul 26, 2016, at 9:55 PM, [ftp83plus] wrote: > >> El 2016-07-26, a las 12:43, Ryan Schmidt escribió: >> >>> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: Here it is:

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

On Jul 26, 2016, at 9:55 PM, [ftp83plus] wrote: > El 2016-07-26, a las 12:43, Ryan Schmidt escribió: > >> >>> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: >>> >>> Here it is: >>> http://pastebin.com/3LRF0bDS >>> >>> Mac OS X 10.6.8, MacBookPro8,1 >> >> >> Ok, so according to that,

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

What's the path to this log? El 2016-07-26, a las 12:43, Ryan Schmidt escribió: > >> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: >> >> Here it is: >> http://pastebin.com/3LRF0bDS >> >> Mac OS X 10.6.8, MacBookPro8,1 > > > Ok, so according to that, MacPorts clang

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

> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: > > Here it is: > http://pastebin.com/3LRF0bDS > > Mac OS X 10.6.8, MacBookPro8,1 Ok, so according to that, MacPorts clang 3.7 is being used to try to configure MacPorts clang 3.4, but MacPorts clang 3.7 is crashing.

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

Here it is: http://pastebin.com/3LRF0bDS Mac OS X 10.6.8, MacBookPro8,1 El 2016-07-26, a las 09:06, Aljaž Srebrnič escribió: >> On 26 lug 2016, at 14:13, [ftp83plus] wrote: >> >> Hello there, >> >> I am currently attempting a "port selfupdate" operation before

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

> On 26 lug 2016, at 14:13, [ftp83plus] wrote: > > Hello there, > > I am currently attempting a "port selfupdate" operation before installing two > ports I'd like to test. > > However, it fails for a reason I don't understand: > Terminal shows: > ---> Verifying

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

Hello there, I am currently attempting a "port selfupdate" operation before installing two ports I'd like to test. However, it fails for a reason I don't understand: Terminal shows: ---> Verifying checksums for clang-3.4 ---> Extracting clang-3.4 ---> Applying patches to clang-3.4 --->