Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#46887 closed defect (fixed)

llvm-3.7 @3.7-r229298 fails building on 10.6.8

Reported by: udbraumann Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: larryv (Lawrence Velázquez)
Port: llvm-3.7

Description

As I was trying to update clang-3.7 from 3.7-r226372_0 to 3.7-r229298_0 I received the following error:

:info:build PrettyStackTrace.cpp:39:8: error: thread-local storage is unsupported for the current target
:info:build static LLVM_THREAD_LOCAL const PrettyStackTraceEntry *PrettyStackTraceHead =
:info:build        ^
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.7/llvm-3.7/work/trunk/include/llvm/Support/Compiler.h:403:27: note: expanded from macro 'LLVM_THREAD_LOCAL'
:info:build #define LLVM_THREAD_LOCAL __thread
:info:build                           ^
:info:build 1 error generated.
:info:build make[1]: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.7/llvm-3.7/work/trunk/lib/Support/Release+Debug+Asserts/PrettyStackTrace.o] Error 1

Anyone able to interpret this message?

Attachments (2)

main.log.gz (128.0 KB) - added by udbraumann 9 years ago.
main2.log.gz (220.1 KB) - added by udbraumann 9 years ago.

Download all attachments as: .zip

Change History (8)

Changed 9 years ago by udbraumann

Attachment: main.log.gz added

comment:1 Changed 9 years ago by mf2k (Frank Schima)

Cc: larryv@… added; jeremyhu@… removed
Owner: changed from macports-tickets@… to jeremyhu@…

comment:2 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

comment:3 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Status: newassigned

comment:4 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: assignedclosed

r133050 should address this for now.

comment:5 in reply to:  4 Changed 9 years ago by udbraumann

Thanks for the work-around. I have relaunched building after cleaning, however, shortly after

:info:build llvm[1]: Linking Release+Debug+Asserts Shared Library libLLVM-3.7svn.dylib

I run into the following linker problem

:info:build Undefined symbols for architecture x86_64:
:info:build   "_environ", referenced from:
:info:build       Execute(llvm::sys::ProcessInfo&, llvm::StringRef, char const**, char const**, llvm::StringRef const**, unsigned int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*) in libLLVMSupport.a(Program.o)
:info:build ld: symbol(s) not found for architecture x86_64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
:info:build make[1]: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.7/llvm-3.7/work/trunk/Release+Debug+Asserts/lib/libLLVM-3.7svn.dylib] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.7/llvm-3.7/work/trunk/tools/llvm-shlib'
:info:build make: *** [all] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.7/llvm-3.7/work/trunk'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.7/llvm-3.7/work/trunk" && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build org.macports.build for port llvm-3.7 returned: command execution failed
:debug:build Error code: CHILDSTATUS 12310 2

I attach the full log file as main2.log.

Last edited 9 years ago by udbraumann (previous) (diff)

Changed 9 years ago by udbraumann

Attachment: main2.log.gz added

comment:6 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

That is another issue, http://llvm.org/bugs/show_bug.cgi?id=22631 llvm.org seems to be down at the moment, but I'll get a fix in sometime soon.

Note: See TracTickets for help on using tickets.