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

[ftp83plus]

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             i386

# Space-delimited list of CPU architectures to target when building
# universal. Defaults to "i386 ppc" on OS X 10.5 and earlier and
# "x86_64 i386" on OS X 10.6 and later.
universal_archs         x86_64 i386


It looks like it will build both arcvhitectures, but i386 is not available for one of them?




El 2016-07-29, a las 01:35, Ken Cunningham escribió:

> 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  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.
> 
> Also - I built everything using clang-3.4 as per the instructions:
> 
> sudo port -v -f deactivate active
> sudo port -v install clang-3.4 ld64 cctools libcxx
> but somehow you seem to be using clang-3.3 .... so something is not quite right there.
> 
> Best,
> 
> Ken
> 
> 
> 
> 
> 
> On 2016-07-28, at 10:19 PM, [ftp83plus] wrote:
> 
>> 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 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/work/build-i386/CMakeFiles/CMakeOutput.log".
>>> Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/work/build-i386" && /opt/local/bin/cmake -DCMAKE_INSTALL_PREFIX=/opt/local/tmp -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_MODULE_PATH=/opt/local/share/cmake/Modules -DCMAKE_FIND_FRAMEWORK=LAST -Wno-dev -DCMAKE_INSTALL_RPATH=/opt/local/lib/libomp -DCMAKE_INSTALL_NAME_DIR=/opt/local/lib/libomp -DCMAKE_C_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.6" -DCMAKE_OSX_SYSROOT="/" -DCMAKE_OSX_ARCHITECTURES=i386 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/work/openmp-381/rc1/runtime 
>>> Exit code: 1
>>> Error: org.macports.configure for port libomp returned: configure failure: command execution failed
>>> Warning: targets not executed for libomp: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install
>>> Error: Failed to install libomp
>>> Please see the log file for port libomp for details:
>>>     /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/main.log
>>> Error: The following dependencies were not installed: libomp llvm-3.8
>>> To report a bug, follow the instructions in the guide:
>>>     http://guide.macports.org/#project.tickets
>>> Error: Processing of port clang-3.8 failed
>> 
>> 
>> Should I open a new topic for this particular error?
>> CMakeOutput.log: http://pastebin.com/f1XYZXcF
>> main.log: http://pastebin.com/5ZPVKug4
>> 
>> Pat
>> 
>> 
>> El 2016-07-28, a las 13:57, Ken Cunningham escribió:
>> 
>>> Hi,
>>> 
>>> I had what appears to be the identical problem a week ago, reported with tickets at Macports and LLVM.org.
>>> Solved as described in the macports ticket.
>>> 
>>> Thanks,,
>>> Ken
>>> 
>>> 
>>> 
>>> Please see:
>>> 
>>> <https://trac.macports.org/ticket/51864>
>>> 
>>> and
>>> 
>>> <https://llvm.org/bugs/show_bug.cgi?id=28592>
>>> 
>>> 
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20160729/10896ec7/attachment.html>