> 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 -Wl,-search_paths_first >>>> -Wl,-headerpad_max_install_names -L/opt/local/lib >>>> -Wl,-headerpad_max_install_names >>>> CMakeFiles/cmTC_70577.dir/testCXXCompiler.cxx.o -o cmTC_70577 >>>> 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 0x 0 ) which is not the architecture being >>>> linked (i386): /usr/lib/libc++.dylib >>> >>> You're building for -arch i386, but your libc++.dylib does not have >>> that architecture (it's likely going to be x64_86) -- So somewhere >>> ( probably in your macports.conf file, I would think) your >>> architecture is not set correctly. >> >> The libomp port is being installed +universal. Since it uses the >> muniversal-1.0 portgroup, MacPorts builds it for each architecture >> separately, then lipo(1)s everything together at the end. >> >> The problem is that the i386 build is trying to link to libc++, which in >> your case appears to be provided by libcxx. But libomp does not declare a >> dependency on libcxx, so MacPorts did not attempt to rebuild libcxx >> +universal. You may have to do this yourself. >> >> vq > > So should I rebuild libcxx +universal variant first before performing Step 4 > of the LibcxxOnOlderSystems?
Jeremy, shouldn't we modify the LibcxxOnOlderSystems instructions to include installing libcxx +universal? _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
