similar to: [LLVMdev] LLVM pre-built libraries download? (OBJ_ROOT structure)

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] LLVM pre-built libraries download? (OBJ_ROOT structure)"

2009 Jul 12
0
[LLVMdev] LLVM pre-built libraries download? (OBJ_ROOT structure)
Hello, Lance > 10:46:08.20 C: mingw32-make > gcc -IC:/MinGW/include -g -c que.cc > que.cc:1:19: stdio.h: No such file or directory > que.cc:2:20: stdlib.h: No such file or directory > que.cc:3:20: string.h: No such file or directory Have you really unpacked mingw-runtime and w32api tarballs? It seems you didn't. -- With best regards, Anton Korobeynikov Faculty of Mathematics
2009 Jul 12
0
[LLVMdev] LLVM pre-built libraries download? (OBJ_ROOT structure)
Hello, Lance > With regards to my original problem, still requires flex/bison to configure, > and I have installed. The problem that brought me to the list turns out to > be that I have a copy of borland/inprises grep tool on the path (which I use > a lot). Heh, name clashing is well-known problem. Another source of such problems is 'sort' util. > Probably not an issue,
2009 Jul 11
4
[LLVMdev] LLVMdev Digest, Vol 61, Issue 25
Hi Anton, The problem is in getting the system configured. Below is the crash I get in configure. Your comment regarding gnuwin32 not being needed is interesting - I actually installed gnu bison/flex to get past an earlier crash in configure. Thats why I was suggesting that a precompiled OBJ_ROOT for MingW32 would be a good idea - configure appears to be inherently fragile, and requires more
2009 May 04
0
[LLVMdev] configure problems under msys
Hello, Bob > download the latest from the head of the trunk, then ran 'configure' under > msys and received the following....  has anyone done this under msys on a > windows pc?? Msys works fine for me. What is the version of msys you're using? What is the version of bash? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State
2009 May 04
2
[LLVMdev] configure problems under msys
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Verdana">download the latest from the head of the trunk, then ran 'configure' under msys and received the following.... has anyone done this
2023 Jan 18
1
Problem installing gdb into Rtools42
On 1/18/23 04:33, Dominick Samperi wrote: > Hello, > > I tried installing gdb into Rtools42 following the instructions here > https://cran.r-project.org/bin/windows/base/howto-R-4.2.html > > I ran 'pacman -Sy gdb', and the installation seemed to complete without > problems. > > But gdb could not be started because incorrect DLL versions were installed, > in
2009 May 04
2
[LLVMdev] configure problems under msys
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Verdana">i running msys 1.0 it appears; the bash sh is
2023 Jan 18
1
Problem installing gdb into Rtools42
Thanks, But this didn't work. It installs msys2 along with lots of other stuff, and gdb would not start as before (missing DLL's). Then I tried to run the command you suggested again, and there was a warning from the package manager about a cycle detected, but now gdb starts with the following messages... Traceback (most recent call last): File "<string>", ine 3, in
2023 Jan 18
1
Problem installing gdb into Rtools42
Hello, I tried installing gdb into Rtools42 following the instructions here https://cran.r-project.org/bin/windows/base/howto-R-4.2.html I ran 'pacman -Sy gdb', and the installation seemed to complete without problems. But gdb could not be started because incorrect DLL versions were installed, in particular, the missing DLL's are: msys-ffi-8.dll and msys-unistring-5.dll. Is there
2023 Jan 18
1
Problem installing gdb into Rtools42
On 1/18/23 17:39, Dominick Samperi wrote: > Thanks, > > But this didn't work. It installs msys2 along with lots of other > stuff, and gdb would not start as before (missing DLL's). > > Then I tried to run the command you suggested again, and there was a > warning from the package manager about a cycle detected, but now gdb > starts with the following messages...
2023 Jan 18
2
Problem installing gdb into Rtools42
On 1/18/23 19:41, Dominick Samperi wrote: > Thanks for the detailed feedback Tomas, > > I ran the command 'pacman -Syuu' again, just to be sure, and this time > it says "there is nothing to do." > > It appears that gdb is working. I was spooked by the diagnostics that > you say is a known (not serious) issue. > > My mistake was not setting a
2023 Jan 18
1
Problem installing gdb into Rtools42
Thanks for the detailed feedback Tomas, I ran the command 'pacman -Syuu' again, just to be sure, and this time it says "there is nothing to do." It appears that gdb is working. I was spooked by the diagnostics that you say is a known (not serious) issue. My mistake was not setting a breakpoint on main, so I confused problems with gdb with problems with the program I'm
2012 Nov 25
2
[LLVMdev] MCJIT and Lazy Function Creators
Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As all "external" functions are provided by the language's FFI mechanism, it does MyExecutionEngine->DisableSymbolSearching(); MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator); which works fine with the JIT. However, MCJIT insists on resolving unknown symbols by searching them
2013 Feb 04
0
[LLVMdev] [cfe-dev] RFC: Promote AArch64 to be built by default
> I think this is the right thing to do. Once you've resolved the Mac and Windows issues, go for it. Thanks Doub. Just to let people know what happened. I enabled in r174322 around lunchtime. Here's a report of the noticed failures with status (important/outstanding ones at the top). Feel free to do anything from telling me about more problems to reverting the patch when llvm.org comes
2023 Jan 19
2
Problem installing gdb into Rtools42
On second thought, there is a lot of metapramming code in Rcpp that runs before main, so I was wrong to say nothing can happen before main() is called. Strategically placed print statements may be the best strategy. On Wed, Jan 18, 2023 at 8:17 PM Dominick Samperi <djsamperi at gmail.com> wrote: > Since these ?stray threads? were appearing before I installed gdb into > Rtools42, this
2008 Apr 28
2
[LLVMdev] Lost in the documentation
In http://llvm.org/docs/FAQ.html, when taking about writing a compiler that uses LLVM (at least I think that's what the FAQ question is asking), the FAQ recommends > # Call into the LLVM libraries code using your language's FFI (foreign > function interface). > > * for: best tracks changes to the LLVM IR, .ll syntax, and .bc > format > * for:
2009 Dec 08
4
[LLVMdev] Rebuilding LLVM libraries with LLVM-GCC on Windows
Hello again, In order to avoid the set jump/long jump dependency of DLLs built under Visual C++, we're trying to build the libraries and tools under LLVM-GCC so it will use DWARF exception handling instead of SJ/LJ. The problem we're running into is that the libraries that we just finished creating cannot be found later in the build process when OPT tries to build. My partner has MinGW
2013 Jan 31
2
[LLVMdev] [cfe-dev] RFC: Promote AArch64 to be built by default
On Jan 31, 2013, at 4:37 AM, Tim Northover <t.p.northover at gmail.com> wrote: > Hi all, > > We'd like to promote the AArch64 backend to being built by default. I > know it's very soon after the initial upload, but we think the backend > is in a good position and should be stable. > > We'd very much like to get it tested in more diverse environments >
2012 Jun 04
2
[LLVMdev] probleam about ThreadLocalImpl of llvm
Hi, everyone: I am very sorry to trouble you, but I need your help about my problem about ThreadLocalImpl in llvm of 2.8 version. I have compiled it in Windows xp with mingw, and have compiled skyeye(an open source project about simulator) as it uses llvm. But when I run a testcase ---- arm_hello, it came out segment fault. I used gdb.exe to trace it, it gave the following infomation: $
2004 Oct 06
2
[LLVMdev] Compiling errors from UnixLocalInferiorProcess.cpp when compiling on MinGW
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