llvm dev - Dec 2009 - [LLVMdev] LLVM MinGW binaries on Vista issue

Hello
> Is anyone successfully running the 2.6 binaries as-is on any windows box?
Yes. They are running successfully since LLVM 1.8 as-is. The usual test
for mingw binaries includes e.g. Qt compilation via llvm-gcc.

-- 
With best regards, Anton Korobeynikov.

Faculty of Mathematics & Mechanics, Saint Petersburg State University.

> > Is anyone successfully running the 2.6 binaries as-is on any windows
box?
> Yes. They are running successfully since LLVM 1.8 as-is. The usual test
> for mingw binaries includes e.g. Qt compilation via llvm-gcc.
Anton,

First, thank you for taking the time to reply.

Looking at the type of issues discussed on this list, this thread cleary
doesn't belong here.  It is little more than noise.  That said, it's not
clear where it should be worked.  Quite frankly, this should already be
documented in the Getting Started doc.  Either I missed it or it's not
there.

Since the mingw binaries are compiling Qt on windows, then my issue should
likely be one of:

* incorrect PATH setup...currently using
"c:\llvm;c:\llvm-gcc\bin;C:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem"
* incorrect dir structure...currently using "c:\llvm" and
"c:\llvm-gcc" as peers...no spaces in dirs...should they be nested?
* missing dependency...e.g. is MSys with a correct /etc/fstab required?

Would you reply with the configuration (llvm* dir layout, PATH, OS flavor,
required dependencies) for the test system successfully using the binaries to
build Qt?

Assuming the info fixes things on my system, what doc should I mod (FAQ, Getting
Started, ??) in order to make this more clear?  I'm assume submitting a
standard diff is preferred.

Thank you,
Jon

Hello, Jon

The main idea of llvm-gcc is to be a drop-in replacement of gcc. So,
if you know how to install & run gcc on your system, you should be
able to do the same with llvm-gcc (thus no "Getting Started" entry).
Basically the only "packaging differences" wrt normal gcc is that
we're shipping w32api & mingw-runtime packages with llvm-gcc. Surely,
you still need binutils installed (to get linker + assembler).
> * incorrect PATH setup...currently using
"c:\llvm;c:\llvm-gcc\bin;C:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem"
Looks ok. However, llvm itself is not required.
> * incorrect dir structure...currently using "c:\llvm" and
"c:\llvm-gcc" as peers...no spaces in dirs...should they be nested?
No. LLVM itself is not required at all, however, no
> * missing dependency...e.g. is MSys with a correct /etc/fstab required?
No, msys is not required (like for normal gcc)
> Would you reply with the configuration (llvm* dir layout, PATH, OS flavor,
required dependencies) for the test system successfully using the binaries to
build Qt?
1. Just ordinary Windows XP SP2 box. No additional stuff installed
2. mingw gcc is installed in the c:\mingw, binutils is unpacked into
the same dir, thus c:\mingw\bin is added to PATH
3. LLVM sources are located in the c:\llvm\src, build directory is
c:\llvm\build, nothing added to PATH
4. llvm-gcc lives in c:\llvm-gcc\bin, nothing added to PATH

If you have problems with invocation of gcc / llvm-gcc it's usually
helps to add -v flag to cmdline to see, what it tries to executed.

Hope this helps.

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University