similar to: [LLVMdev] parsing windows.h in llvm clang

Hi What did I start? <*shrug*> Well, well, well. First a little bit of history: I joined the LLVM project, because the ideas sounded very interesting to me and I voluntered for a minor patch for prefetch datasupport for the gcc-compiler. At that time, when I joined, the only possibility to develop on the windows platform was to use Cygwin Unix Windows emulation layer, but it had some

Could someone running Cygwin or involved in Cygwin help this person please? - Ben ---------- Forwarded message ---------- Date: Thu, 17 Oct 2002 17:58:45 -0400 From: Andrew Greene <agreene at pageflexinc.com> To: openssh at openssh.com Subject: Upgraded to latest cygwin this morning, and ssh refuses to enter binmode. Help! I upgraded to the latest cygwin this morning (not sure when

Andrew, This might be offtopic for llvmdev. I suggest the mailing list, cfe-users. > * clang.exe version 3.4 (trunk), from LLVM 3.4.svn How did you build it? clang.exe depends on crt libraries, either mingw32 or msvcrt. Please try (and watch their output); > clang --version > clang -v -O2 -o hello.exe hello.c Please confirm; - Which library did you install? Visual studio or

Richard Smith wrote: > I am working on a port of LLVM targeting a proprietary VM. Thus far > development has been under Linux and Cygwin. Cygwin licensing would appear > to require that LLVM built under Cygwin would have to be released under the > GPL, so alternatives are being investigated. > > Using MS Visual Studio and following the instructions at >

Ted Neward wrote: > > Trying to just get some idea of what parts are necessary when using > (not necessarily building, if I can help it) LLVM 2.0 on a Win32 machine. > I don't use LLVM on Win32, so I'm don't know the answers to all of your questions. However, the developers who ported LLVM to Win32 are on the llvmdev mailing list. I'm forwarding this to llvmdev in

Samuel Crow wrote: > Are you still using Cygwin? > Why not try using MinGW instead. It was available. I live in Cygwin; MSYS is a poor alternative. Also generally speaking, open source projects targeting a POSIXy environment have a higher probability of working first time with Cygwin, so it serves well for investigation (e.g. no distribution in the GPL sense). > I think Cygwin cannot

On May 11, 2008, at 9:36 AM, Óscar Fuentes wrote: > > Not that I sympathize with the OP's manners but... > > Bill Wendling <isanbard at gmail.com> writes: >> >> That's only a convenience. GCC generates assembly code too and calls >> the assembler and linker as part of it's execution. You are perfectly >> able to call the assembler & linker

Hello, I'm trying to use LLVM on Windows, using the MinGW toolchain that comes with Cygwin (gcc -mno-cygwin, not the standalone msys package). Has anyone successfully built LLVM from sources with this toolchain? The ./configure scripts automatically detects a Cygwin environment. I've spent some time trying to let it know that it should compile for MinGW. FWIW, here's what I've

I have got the latest CVS release of LLVM. And built the Win32 MS VC++ 2003 port with modifications for MS VC++ 2005. Do bear in mind the Visual Studio ports are by no means complete, and are on going. Microsoft Visual Studio 2005 Beta (codename Whidbey) can be got from Microsoft Beta program nearly for free; the cost of postage from :-

Evan Jones wrote: > On Nov 23, 2005, at 22:49, Jeff Cohen wrote: > >> News to me. I do it all the time. Notice the "win32" directory >> under the root :) > > > Okay, so I spoke about something that I don't really know about, since > I don't use Windows. But what was the whole "Still can't compile > backend of frontend on

I am working on a port of LLVM targeting a proprietary VM. Thus far development has been under Linux and Cygwin. Cygwin licensing would appear to require that LLVM built under Cygwin would have to be released under the GPL, so alternatives are being investigated. Using MS Visual Studio and following the instructions at http://llvm.org/docs/GettingStartedVS.html (Getting Started with the LLVM

Hi, Whenever i am using the command rsync --write-batch -av --stats `cat $1` -e ssh user@remote machine:/destination/ This is writing rsync_argvs files in the home directory as well as to the destination directory. Can anyone give me any idea as how to prevent the writing of rsync_argvs files in the home directory which is of no use. Regards, Surabhi. > ---------- > From:

2 more roadblocks for Visual Studio users are the inability to compile gcc and the inability to compile and run the test suite. I would not want to submit a change unless I could still compile/run gcc and pass the test suite. (Testing before submission is the way we do it where I come from - I am assuming it's the same here). On a related note, has anyone gotten the LLVM test suite working

On Wed, 2005-02-16 at 19:52, Aaron Gray wrote: > Hi Reid, > > I'll send a complete report tommorow, its getting late. Great! > > It looks like there is alot of work to do to get the MS VC version in line > with the Unix release. I am very willing to help out with porting. Yes, there are several well known issues remaining. The bugpoint tool and the debugger use unix

On Wed, Jun 27, 2012 at 3:10 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > David Röthlisberger <david at rothlis.net> > writes: > > > On 21 Jun 2012, at 01:19, Chandler Carruth wrote: > >> cmake, while ugly, can be made to support all of our use cases. There > >> are some use cases that autoconf+make can't support, > > > > So far I

Hi, Has anyone built llvm-gcc-4.2-2.9 using mingw-w64 on Windows 7 64-bit OS? The binaries available in the download website LLVM-GCC 4.2 Front End Binaries for Mingw32/x86<http://llvm.org/releases/2.9/llvm-gcc4.2-2.9-x86-mingw32.tar.bz2> do not build applications (not surprisingly) for 64-bit Windows 7 (-m64 is disabled). I am both compiling and linking an application (to produce a

Giorgio Franceschetti <g.franceschetti at vidya.it> writes: > I also tried to build LLVM with 3.3 sources. > Same problems. If you omit compiler-rt, does it work? (compiler-rt is not a required component.) > Even worse, Visual Studio hangs and I had to kill the process. > > What could it be? Is Visual Studio 2012 working with LLVM/clang? > > Or LLVM/Clang is not

I've followed all the LLVM+clang build-from-source instructions for Windows using MSVC++ 2008. It all builds fine. I initially had troubling getting any linking to work at all until I made sure to have the right environment variables set using a wrapper batch script. Now C programs compile, link, and execute fine, but C++ programs don't link, not even a simple "hello, world"

Thanks for your reply. Compiler-rt was a problem. From the documentation I thought it was mandatory (so what is it used for?), but it was giving all those error about stdbool.h missing that I reported. Now things got better, but I have still problems. I receive an error that seems related to the fact that the grep command is missing. Is it possible? If grep is needed, how can I found it in

Jonathan Brumley wrote: > > 2 more roadblocks for Visual Studio users are the inability to compile > gcc and the inability to compile and run the test suite. I would not > want to submit a change unless I could still compile/run gcc and pass > the test suite. (Testing before submission is the way we do it where > I come from - I am assuming it's the same here). >