search for: exported_symbol

....dll by perfoming 'make' in $LLVM_SRC_DIR/runtime/libprofile. After make, I got the following error messages. llvm[0]: Linking Debug+Asserts Loadable Module profile_rt.dll /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:/cygdrive/c/ llvm/runtime/libprofile/Debug+Asserts/exported_symbols.lst: file format not reco gnized; treating as linker script /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:/cygdrive/c/ llvm/runtime/libprofile/Debug+Asserts/exported_symbols.lst:2: syntax error collect2: ld returned 1 exit status make: *** [/cygdrive/c/llvm/Debug+Asserts/bin/...

...owing document provides good summary... http://developer.apple.com/documentation/DeveloperTools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html#/ /apple_ref/doc/uid/TP40001670 Another way to control symbol visibility is to use linker's interface. See ld man page for more info on -exported_symbols_list, - exported_symbols, -unexported_symbols_list etc.. flags. If you're going to try this approach, pl. read ld man page first. - Devang

On Sun, Jan 25, 2009 at 11:38:48AM +0100, Jean-Daniel Dupas wrote: > > Le 25 janv. 09 à 06:01, Jack Howarth a écrit : > > > After trying the recommended use of -O4 -fvisibility=hidden to > > compile xplor-nih with full LTO optimizations, I discovered three > > symbols become undefined... > > > > llvm-gcc-4 -O4 -fvisibility=hidden -o xplor xplor.o \ >

...libc.so.6 0x00002aaaabaaf1a6 __libc_start_main + 230 22 llvm-ld 0x00000000006aa039 __gxx_personality_v0 + 689 Stack dump: 0. Program arguments: .../llvm-svn-debug-obj/Debug/bin/llvm-ld -L.../llvm-van-install/bin/../lib -internalize-public-api-file=.../llvm-svn/runtime/libprofile/exported_symbols.lst -o .../llvm-svn-debug-obj/runtime/libprofile/Debug/profile_rt.internalize .../llvm-svn-debug-obj/runtime/libprofile/Debug/BasicBlockTracing.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/BlockProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/CommonProfiling.bc .../llvm-svn-debug...

...summary... > > http://developer.apple.com/documentation/DeveloperTools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html#/ > /apple_ref/doc/uid/TP40001670 > > Another way to control symbol visibility is to use linker's interface. > See ld man page for more info on -exported_symbols_list, - > exported_symbols, -unexported_symbols_list etc.. flags. If you're > going to try this approach, pl. read ld man page first. > - > Devang > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu...

...___emutls_get_address Referenced from: /usr/lib/libc++abi.dylib Expected in: flat namespace Trace/BPT trap Adding -Wl,-flat_namespace does not make the symbols visible. If I try to fix it like this by forcing the symbol to be exported, I get a clue: $ clang++ -std=c++11 -stdlib=libc++ -Wl,-exported_symbol,___emutls_get_address -o 4 4.cpp ld: warning: cannot export hidden symbol ___emutls_get_address from /opt/local/libexec/llvm-5.0/lib/clang/5.0.1/lib/darwin/libclang_rt.osx.a(emutls.c.o) Things do work apparently properly however if I build emutls.c directly into libc++abi.dylib, using a slightly...

On Tue, Jun 6, 2017 at 11:14 PM, Michael Clark via llvm-dev < llvm-dev at lists.llvm.org> wrote: > OK. I see that the Mach-O linker is not even built when LLD is enabled in > Release_40, only the PE/COFF and ELF linkers are built. > > From looking at reviews it appears that Clang was able to be linked with > LLD on Darwin about 2 years ago, so Mach-O support seems to have