search for: ldbghelp

Yes, that's my understanding, too. But I'm not controlling where my library -ldbghelp is put when g++ is called. I just put it in the TOOLLINKOPTS variable in Makefile.config. Henrik >From: Reid Spencer <reid at x10sys.com> > >John Criswell wrote: >> >>It seems that the -L path options are specified before the LLVM libraries >>(libSystem and libs...

Henrik Bach wrote: > Hi LLVM'ers > > When linking tblgen tool I get below error message on MinGW. > > I have put TOOLLINKOPTS=-ldbghelp in Makefile.config. > > However, when rearranging library dbghelp to the end of the g++ > line, tblgen gets linked. It seems that the -L path options are specified before the LLVM libraries (libSystem and libsupport) are linked in. I think g++ may only search linker paths that are spe...

Hi LLVM'ers When linking tblgen tool I get below error message on MinGW. I have put TOOLLINKOPTS=-ldbghelp in Makefile.config. However, when rearranging library dbghelp to the end of the g++ line, tblgen gets linked. -------------------------- make[2]: Entering directory `/C/Projects/build/MinGW/llvm/utils/TableGen' Linking Debug executable tblgen /C/Projects/build/MinGW/llvm/mklib --tag=disable-s...

>So, if I'm understanding you correctly, libdgbhelp is a library that >doesn't come with MinGW but can be installed on MinGW by the user if it is >needed. Am I correct? Yes. >If that's the case, I would say that it's the user's reponsibility to >install the library into /usr/lib or provide the configure script with the >appropriate -L options to find it

Henrik Bach wrote: >> From: John Criswell <criswell at cs.uiuc.edu> >> Date: Mon, 25 Oct 2004 15:38:52 -0500 > > >> >> When you run configure, you'd do something like this: >> >> configure --prefix=<...> LDFLAGS="-L<path where libdgbhelp is installed" >> >> If you modify Makefile.config directly, just add the

>From: John Criswell <criswell at cs.uiuc.edu> >Date: Mon, 25 Oct 2004 15:38:52 -0500 > >When you run configure, you'd do something like this: > >configure --prefix=<...> LDFLAGS="-L<path where libdgbhelp is installed" > >If you modify Makefile.config directly, just add the necessary -L option to >TOOLLINKOPTS. I believe that should fix

>From: John Criswell <criswell at cs.uiuc.edu> >Will this library be needed for tblgen or for all LLVM programs? And is it >a library you wrote for LLVM, or is it a MingW library? It's is generally needed for all programs or at least programs using Signals.o (from platform/Signals.cpp) and it is platform/MinGW specific. >TOOLLINKOPTS is used by configure to convey

...ES = $(LLVM_LIB_PATH)LLVMX86.o \ $(LLVM_LIB_PATH)LLVMExecutionEngine.o \ $(LLVM_LIB_PATH)LLVMJIT.o \ -lLLVMAsmParser \ -lLLVMSelectionDAG \ -lLLVMCodeGen \ -lLLVMScalarOpts \ -lLLVMTransformUtils \ -lLLVMAnalysis \ -lLLVMTarget \ -lLLVMCore \ -lLLVMSupport \ -lLLVMSystem \ -lpsapi \ -ldbghelp If you are on VS, .o is .obj and -lLLVMWhatever is Whatever.lib. If you still have problems, examine the commands that are executed for building some example (examples/Fibonacci/fibonacci.cpp for instance). HTH -- Oscar

...o for me). 4. cd to `temp'. 5. Execute this: for f in ../lib*.a ; do ar x $f ; done If you are working on the LLVM's debug install, do: rm Debugger.o ProgramInfo.o RuntimeInfo.o SourceFile.o SourceLanguage*.o 6. Then: g++ -shared --export-all-symbols -o LLVM.dll *.o -lpsapi -ldbghelp This may require several minutes and use approx. 0.5 GB. If you are working on LLVM's debug install, it is a good idea to name the dll LLVMd.dll or something to differentiate it from the release build. 7. This creates LLVM.dll. Move it to LLVM's /lib directory. Put a copy s...

Hello all, I'm trying to bring an LLVM-based project that is working on Linux up on Win32. I am having problems with llvm::ExecutionEngine::create returning a NULL. I traced it to these lines: // Unless the interpreter was explicitly selected, try making a JIT. if (!ForceInterpreter && JITCtor) EE = JITCtor(MP, ErrorStr); // If we can't make a JIT, make an

Hi Reid, I don't think I've initiated a parallel build by this command: ------------------------ make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1 ------------------------ Henrik. >From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800 > >It looks like what you're getting is a sharing violation. Although, I >don't understand why. The llvm-ar.e...

...this, does this not work on MinGW? > 5. make CFLAGS=-O LIBCFLAGS+=-g LIBCFLAGS+=-O2 LIBCXXFLAGS+=-g LIBCXXFLAGS+=-O2 Why CFLAGS=-O? Why not -O2? Can the other flags be combined like this: LIBCFLAGS+="-O2 -g" LIBCXXFLAGS+="-O2 -g" for brevity? > 8. make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi Same issue as above. > 10. Not all is working yet: Test the newly-installed C frontend by one > or more of the following means: This isn't clear. What works and what doesn't? What's the status of the CFE on MinGW? > An Example Using the LLVM Tool C...

...s of >verbose output? > >Thanks, > >Reid. > >On Wed, 2005-01-26 at 12:15, Henrik Bach wrote: > > Hi Reid, > > > > I don't think I've initiated a parallel build by this command: > > > > ------------------------ > > make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi > > LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1 > > ------------------------ > > > > Henrik. > > > > >From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800 > > > > > >It looks like what you're getting is...

Hi LLVM'ers, Here is my second try to document, how to build the llvm system for MinGW on Windows. Henrik. ============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= 'Nothing is impossible; The impossible just takes longer time :)' -

It looks like what you're getting is a sharing violation. Although, I don't understand why. The llvm-ar.exe when its building an archive file always builds it in a temporary. Only when that is complete does it remove the old one and rename the temporary. Perhaps this is a result of doing parallel build and the "lib3.tmp" file (that name looks wrong to me) is being accessed by

Hi Jeff and others, When building the llvm runtime, I always get this error message: 'Can't destroy file: The process cannot access the file because it is being used by another process.' The file is destoyed anyway. I think that the the real error is the path for the file (*/\file.tmp). However, I can't find the bug in the source. Do you have any clue?: