similar to: [LLVMdev] Getting started using MinGW binary release?

> Sorry, this wasn't mentioned in documentation. llvm-gcc was built with > '--enable-threads' flag, thus it requires win32 pthread port. Keith have > already given a right link for dlls download. Just to make stuff clear: you'll have to download pthreadGC1.dll, rename it to pthreadGC.dll and put it somewhere in your PATH. All try to build all future versions of binaries

Finally, I got my hands on Windows machine again today. I extracted llvm-2.1-x86-mingw32.tar.bz2 and llvm-gcc4.0-2.1-x86-mingw32.tar.bz2 to C:\llvm (It's a bare Windows Vista installation without MinGW) Added C:\llvm\bin;C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 to PATH (C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 was added for cc1.exe) Downloaded

Ted, > When I try to run lli hello.bc, I get an unsatisfied DLL link error: "This > application has failed to start because pthreadGC.dll was not found." > Hunting around I can't find this DLL anywhere; where should it have come > from? pthreads are required for LLVM. Easy googling ("pthreads mingw32) returns the following place for dlls download:

Hi. >From http://llvm.org/docs/GettingStarted.html , it seems I have to build LLVM from source. But I found http://llvm.org/releases/2.1/llvm-2.1-x86-mingw32.tar.bz2 . When I extract the file, I get many binaries (lli.exe, llc.exe...etc). When I run lli.exe, I get: lli.exe - Unable To Locate Component This application has failed to start because pthreadGC.dll was not found.

More bison woes. llvm-2.1 + the patch Chris mentioned builds without bison, but llvm-gcc4 doesn't: /home/emil/ll/llvm-gcc4.0-2.1.source/missing bison -d -o gengtype-yacc.c ../../llvm-gcc4.0-2.1.source/gcc/gengtype-yacc.y WARNING: `bison' missing on your system. You should only need it if you modified a `.y' file. You may need the `Bison' package in order for

Am Samstag, den 22.03.2008, 09:45 -0500 schrieb Andrew Lenharth: > officially support for llvm-gcc4.0 has been dropped. > unofficially I still keep llvm-gcc4.0 compiling because I need it for > some stuff. But this will only last until I can use 4.2. OK, that's a clear roadmap. Maybe the docs should be updated to reflect this status? They still present 4.0 as if it were the default

Hello, Jonathan > I thought I'd messed up something related to the linker, > but I couldn't explain why XP would work using the same steps. The only thing comes to my mind seeing this: perl from msysDTK works differently (somehow) on Vista, thus llvm-config is broken which leads to missed libraries, broken dependencies, etc. I'd suggest you to compare stuff on different

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

officially support for llvm-gcc4.0 has been dropped. unofficially I still keep llvm-gcc4.0 compiling because I need it for some stuff. But this will only last until I can use 4.2. Andrew On Sat, Mar 22, 2008 at 5:00 AM, Joachim Durchholz <jo at durchholz.org> wrote: > Hi all, > > I'm wondering what the comparative status of llvm-gcc4.0 vs. llvm-gcc4.2 > is. Can anybody

On Mar 22, 2008, at 3:37 PM, Joachim Durchholz wrote: > Am Samstag, den 22.03.2008, 09:45 -0500 schrieb Andrew Lenharth: >> officially support for llvm-gcc4.0 has been dropped. >> unofficially I still keep llvm-gcc4.0 compiling because I need it for >> some stuff. But this will only last until I can use 4.2. > > OK, that's a clear roadmap. > Please do not rely

Anton Korobeynikov wrote: > Hello, Jonathan > > >> I thought I'd messed up something related to the linker, >> but I couldn't explain why XP would work using the same steps. >> > The only thing comes to my mind seeing this: perl from msysDTK works > differently (somehow) on Vista, thus llvm-config is broken which leads > to missed libraries,

Hi all, I'm wondering what the comparative status of llvm-gcc4.0 vs. llvm-gcc4.2 is. Can anybody tell? (A URL would be fine, I may have been just too dumb to find it.) Regards, Jo

> I've run the test last night to see how long it takes, and I can > afford to cronjob it for the night. Great! > I didn't quite realize it would automatically send the report, but > it did [1] and there are a few test failure from the > Frontend{C,C++} directories. I suppose this is because I have > llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is >

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

Hello, Everyone. Now I have some spare time and I've decided to build LLVM on Mingw. I've grab the latest 1.7 release (not CVS snapshot). Here are some issues fixed during the build. Now I'm preparing gcc build. So, I think, there will some other "parts" 1. Prerequisites 1.1 GCC 3.4.5 from mingw.org site. $ gcc --version gcc.exe (GCC) 3.4.5 (mingw special) Copyright (C)

On 07/01/2015 5:20 PM, Jeroen Ooms wrote: > On Wed, Jan 7, 2015 at 8:00 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> This version includes only minor updates to the tools. I indicated last summer that I was hoping to update GCC from the current version 4.6.3 before the R 3.2.0 release, but this now looks unlikely, unless someone else with experience building

Hello list! Tanya Lattner wrote: > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. I've run the test last night to see how long it takes, and I can afford to cronjob it for the night. I didn't quite realize it would automatically

I'm using a little shell script: BUILD_ROOT=/home/llvm-1.7/cfrontend PREFIX="$BUILD_ROOT/install" LOCAL_BUILD_DIR="$BUILD_ROOT/build" SOURCE_DIR="$BUILD_ROOT/src" echo $__me: Building $TARGET echo $__me: BUILD_ROOT == $BUILD_ROOT echo $__me: SOURCE_DIR == $SOURCE_DIR echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR echo $__me: PREFIX == $PREFIX

Anton Korobeynikov <asl at math.spbu.ru> writes: [snip] > 2) Problem: Complains about gthr-default.h file. > Resolution: Grab gcc/gcc/gthr-win32.h file and copy it to gthr-default.h ... so --enable-threads=win32 is broken... good to know. > 3) Problem: Complains about "CL_ObjCXX" and simular ("CL_") during > compilation

>> llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind >> that you need to keep llvm-gcc in sync with llvm (same revision number). > > This basically means llvm-gcc needs to be rebuild every time llvm > is built and the test run. Shouldn't this be part of > NewNightlyTest.pl then? Yes. Patches accepted ;) There is a GSOC student that is supposed