similar to: [LLVMdev] Link error with TOOLLINKOPTS=-ldbghelp on MinGW

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.

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

>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

>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

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

>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

"Aaron Dwyer" <llvmification at gmail.com> writes: [snip] > JITCtor and InterpCtor are both NULL, so it's obvious why I'm getting > back a NULL execution engine. I am pretty sure it's because I'm > missing a few llvm .lib or .obj files. What is the set of llvm object > files needed at link time for Win32 on X86 JIT? This is what I use on MinGW. It

Hi I'm compiling: /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp on MinGW. However, it stops complaining about that SIGALRM is undeclared: -------------------------- @ /usr/local/build/llvm/mklib --tag=disable-shared --silent --tag=CXX --mode=compile g++ -c -I/usr/local/build/llvm/lib/Support -I/usr/local/src/llvm/lib/Support -I/usr/local/build/llvm/include

Reid, >Well, if it doesn't break anything else, I'd fix the header file. The >standard type name is supposed to uint64_t not u_int64_t. I would just >change the header file to define both of them, something like: > >typedef u_int64_t uint64_t; > >You could do that in /usr/include/types.h, I've tried it and it doesn't break anything, but ... >or we could

Hi Can someone tell me, which files you get in the confstat* directory, when running: ./config.status -d /Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- _________________________________________________________________ Opret en gratis Hotmail-konto http://www.hotmail.com med udsigt til 250 MB lagerkapacitet

Hi I've started to port LLVM to the MinGW Win32 platform. To successfully recognize the platform, following statements should be inserted into the configure script: ---------- Index: configure ================================================================== RCS file: /var/cvs/llvm/llvm/configure,v retrieving revision 1.114 diff -u -r1.114 configure --- configure 7 Sep 2004 18:04:45 -0000

Hi, I get below error: --------------------------------- In file included from /usr/local/build/llvm/lib/System/platform/Path.cpp:23, from /usr/local/src/llvm/lib/System/Path.cpp:27: /usr/local/build/llvm/lib/System/platform/../Unix/Path.cpp: In member function `bool llvm::sys::Path::create_directory(bool)': /usr/local/build/llvm/lib/System/platform/../Unix/Path.cpp:343:

Hi As shown below, the .\configure script found a version of stat.h: --------------------- configure:4382: checking for sys/stat.h configure:4399: gcc -c -g -O2 conftest.c >&5 configure:4402: $? = 0 configure:4405: test -s conftest.o configure:4408: $? = 0 configure:4419: result: yes --------------------- However, I got this error when compiling: --------------------- FileUtilities.cpp:

Henrik Bach wrote: > Hi > > I'm compiling: /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp > on MinGW. However, it stops complaining about that SIGALRM is undeclared: Is there an alarm() syscall on MinGW? And if so, what signal does it send (according to the MinGW docs)? -- John T. > -------------------------- > @ /usr/local/build/llvm/mklib

Ultimately, this is another function that needs to go into lib/System. An alternate approach is to fork a thread, sleep, and when the thread wakes up, "ring the alarm". Reid. John Criswell wrote: > Henrik Bach wrote: > >> Hi >> >> I'm compiling: >> /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp on MinGW. >> However, it stops

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

Hi When compiling UnixLocalInferiorProcess.cpp, I get these errors: ----------------------- C:/MinGW/msys/local/projects/src/llvm/lib/Debugger/UnixLocalInferiorProcess.cpp:41:22: sys/wait.h: No such file or directory C:/MinGW/msys/local/projects/src/llvm/lib/Debugger/UnixLocalInferiorProcess.cpp: In member function `void <unnamed>::IP::startChild(llvm::Module*, const

Hi, I get this error: ------------------ ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) ToolRunner.cpp:396: error: (Each undeclared identifier is reported only once for each function it appears in.) ------------------ And the config.log shows that configure has detected that ld on my platform (Interix) doesn't support shared libraries: ------------------

Hi again Does cygwin support shared libraries. And if not, how did you port llvm on this issue? /Henrik >From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Tue, 27 Jul 2004 00:41:53 +0200 > >Hi, > >I get this error: >------------------ >ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >ToolRunner.cpp:396:

As the LLVM build does not create dll's on Windows, two problems arises: 1. Static linking creates big executables. 2. Link time is long. We can create dll's on MinGW using a feature of binutils that mimics .so files on GNU/Linux. The process is very simple. On a MSYS or Cygwin shell (make sure MinGW binaries are on the path before Cygwin's). Read all message before rolling up