similar to: [LLVMdev] Re: Still can't compile backend or frontend on, Windows

llvmdev-request at cs.uiuc.edu wrote: >Send LLVMdev mailing list submissions to > llvmdev at cs.uiuc.edu > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >or, via email, send a message with subject or body 'help' to > llvmdev-request at cs.uiuc.edu > >You can reach the person managing the list at

It's a shame this fine tool can't get better installation support for Windows. If it did I suspect it would get a lot more coverage. After 5 months or so I still have no way to compile the backend tools let alone the C frontend on windows. I have tried both Cygwin and Mingw so far. MingW is preferrable since distributions of the binaries would not require the cygwin.dll. It

On Sat, 29 Oct 2005, Matthew Bromberg wrote: > It's a shame this fine tool can't get better installation support for > Windows. If it did I suspect it would get a lot more coverage. After 5 Yup. > months or so I still have no way to compile the backend tools let alone the C > frontend on windows. I have tried both Cygwin and Mingw so far. MingW is > preferrable

>From: Matthew Bromberg <mattcbro at earthlink.net> >Date: Tue, 01 Nov 2005 16:21:34 -0500 >The JIT compiler is of course of great interest, but I'm also interested in >static compilation and in fact this seems to me one of the intriguing >features of LLVM, the fact that it can support both static and dynamic >languages, with a common optimization infrastructure. (I

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

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

On Tue, 1 Nov 2005, Matthew Bromberg wrote: >> It is the goal to generate OBJ files directly, though that is not likely to >> happen in the near future. But there are other options that do work today. >> The JIT does work, so you can execute programs compiled via LLVM right now. >> Additionally, you can generate C code that you can then compile with VC++, >>

There's simply no equivalent to signals on Windows. There is no way to asynchronously interrupt a thread's processing to execute some handler. The only thing you can asynchronously do to a thread is kill it, and that's generally frowned upon (who knows what critical sections it might be holding, etc...). Stuff like alarms is supposed to be done using the "event-driven"

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

>From: Reid Spencer <reid at x10sys.com> >Date: Fri, 24 Sep 2004 13:03:44 -0700 > >I just discovered that the *only* place this is used is in the debugger >when it is loading files, etc. There should be a way to do this without an >alarm. In fact, a thread could easily set the "ShouldShowStatus" every >second until the the thing is cancelled. Since the

To be more specific: Lines containing SIGALRM and alarm(). >From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Fri, 24 Sep 2004 23:21:58 +0200 > >>From: Reid Spencer <reid at x10sys.com> >>Date: Fri, 24 Sep 2004 13:03:44 -0700 >> >>I just discovered that the *only* place this is used is in the debugger >>when it is loading

Since the 1.8.4 One-click installer is based on VC++ 6.0 which is no longer available, I am looking for alternative ways of building win32-utils so as avoid segfaults. Has anyone used MingGW successfully? When I run ruby extconf.rb from MSYS the resulting make file assumes that I am using VC++. Do I need to build ruby under MinGW first? -- John-Mason Shackelford Software Developer Pearson

Albert Graef <Dr.Graef at t-online.de> writes: >> Some points you mention on your web page are solved. > > Which ones? (Just curious.) No cross-compilation. C99 compiler check missing: You can check the compiler support for a flag with just one line. pkg-config support broken. My understanding is that it is fixed. >> Others are not applicable to LLVM. > > That

Hi, I'm developing an R/TclTk application which uses the BWidget and Tktable Tk extensions and I'm trying to make it easy to install. For now, I'm focusing on Windows users who start with nothing. I have built Tcl/Tk and Tktable for windows using Msys/MinGW. (BWidget contains only Tcl scripts so does not need building.) I have then copied Tktable and BWidget into the lib subdirectory

Kenneth Boyd <zaimoni at zaimoni.com> writes: [snip] >> That does not really surprise me about CMake, but then mingw is not a >> primary compiler on Windows, more so is VC++ or Intel, either way a >> bug should be submitted to the CMake devs. > I do not want to troll the CMake devteam, so I will not submit the bug > report without a full-blown patch. The CMake

OvermindDL1 wrote: > On Sat, Oct 11, 2008 at 7:30 AM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > >> At the absolute minimum, simple counting of the success/failure/internal >> error results requires three different exit codes, and a test driver >> capable of tallying them up and reporting all failures (unexpected >> success, unexpected failure, and

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

Everyone. I had a conversation with folks from Microsoft today about trying to move Ruby''s installer to Visual Studio 2005 and WiX (the MSI installer). They''re quite serious about trying to get us shifted to modern compiler technology rather than VC++6 or even MSYS/MINGW. I can''t say that I disagree with them, either. However, I indicated that one of the big problems

Hi I've been able to semi compile (i.e. excluded code not present on the platform) the source code of the LLVM tblgen tool on the MinGW platform. However, when linking the object files the linker does not succeed: -------------------------- Linking tblgen debug executable (without symbols) C:/MinGW/msys/local/build/llvm/lib/Debug/libLLVMsystem.a(Signals.o)(.text+0x7e3): In function

This file (UnixLocalInferiorProcess.cpp) is due for porting and placement in lib/System but I haven't gotten there yet. If you come up with something that works on MINGW, please let me know. Thanks, Reid. Henrik Bach wrote: > Hi > > When compiling UnixLocalInferiorProcess.cpp, I get these errors: > ----------------------- >