search for: ___eprintf

Cross-compiling from Ubuntu 8.04 x86_64 to mingw with the cmake build system fails with this error while linking some tools: ../../lib/libLLVMSystem.a(DynamicLibrary.cpp.obj):DynamicLibrary.cpp:(.text+0x367): undefined reference to `___eprintf' ___eprintf is mentioned in lib/System/Win32/DynamicLibrary.inc. This symbol is referenced by libLLVMSystem.a when LLVM is natively built on Windows/Mingw, but there the link succeeds. So, is this a cross-compiler issue? OTOH, the build complains about this: /usr/lib/gcc/i586-mingw32msvc/4....

Hello, Oscar > oscar at qcore:~/dev/llvm/mingw-x$ i586-mingw32msvc-g++ --version > i586-mingw32msvc-g++ (GCC) 4.2.1-sjlj (mingw32-2) Have you tried to build llvm natively with exact same compiler version? AFAIR, someone reported, that either this was not possible or there was a miscompilation. PS: Everything is with crosscompilation via gcc 3.4.6 & ld 2.18 -- With best regards, Anton

...I'm attempting to link my frontend - compiled with clang - against the LLVM libraries - compiled with gcc. (I thought about compiling LLVM with clang, but then I'd have to compile it twice to bootstrap.) Under OS X, I get the following error when I try to link: Undefined symbols: "___eprintf", referenced from: ___eprintf$non_lazy_ptr in libLLVMSupport.a(SearchForAddressOfSpecialSymbol.cpp.o) ld: symbol(s) not found clang-3: error: linker command failed with exit code 1 (use -v to see invocation) As you can see the reference is coming from the LLVM libs. Under Ubuntu, t...

...d with clang - > against the LLVM libraries - compiled with gcc. (I thought about > compiling LLVM with clang, but then I'd have to compile it twice to > bootstrap.) > > Under OS X, I get the following error when I try to link: > > Undefined symbols: > > "___eprintf", referenced from: > > ___eprintf$non_lazy_ptr in > libLLVMSupport.a(SearchForAddressOfSpecialSymbol.cpp.o) > > ld: symbol(s) not found > > clang-3: error: linker command failed with exit code 1 (use -v to > see invocation) > Interesting....

...f the terminal): ... Loading required package: grDevices Loading required package: mvtnorm > 2006-06-01 01:06:58.007 R[28814] CFLog (21): Error loading /Users/ > mk/Library/Application Enhancers/FruitMenu.ape/Contents/MacOS/ > FruitMenu: error code 4, error number 0 (Symbol not found: ___eprintf > Referenced from: /System/Library/Frameworks/QuickTime.framework/ > Versions/A/QuickTime > Expected in: /Library/Frameworks/R.framework/Resources/lib/libstdc > ++.6.dylib > ) The following object(s) are masked _by_ .GlobalEnv : .Traceback The following object(s) are ma...

The next problem I have is: llvm[2]: Linking Debug executable opt /home/foad/llvm/objdir-mingw/Debug/lib/libLLVMSystem.a(DynamicLibrary.o):/home/foad/svn/llvm-project/llvm/trunk/lib/System/Win32/DynamicLibrary.inc:179: undefined reference to `___eprintf' collect2: ld returned 1 exit status I can work around this by removing the two references to __eprintf from lib/System/Win32/DynamicLibrary.inc, but... why are they there in the first place, and why don't I have __eprintf on my system? I see that these references were introduced here: h...

I'm trying to cross-compile LLVM with build=, host=target=. I'm using the following packages from Debian lenny: mingw32 4.2.1.dfsg-1 mingw32-binutils 2.18.50-20080109-1 mingw32-runtime 3.13-1 The first problem I hit was when I configured with CC, CXX, AR and RANLIB set to mingw cross-tools, but forgot to specify NM as well. This resulted in a load of warnings that scrolled off the