similar to: [LLVMdev] LLVM+Win32 == Working great

On Mon, 13 Sep 2004, Reid Spencer wrote: > These are all reasons why the Win32 port doesn't exist today. LLVM is Well, the reason it doesn't exist today is that noone has worked on it. :) > heavily influenced and implemented by Unix tools/concepts/facilities. > Since building on Win32 will also be a problem, I think that we should > just target cygwin as our Win32 solution

On Fri, 21 Jan 2005 12:14:41 -0800, Reid Spencer <reid at x10sys.com> wrote: > > Sorry for the sad state of the cygwin build. I had hoped to have it > cleaned up by now but many other things have been taking my time. > Although the build has been succeeding in recent days, I'm not sure it > will buy you anything. NONE of the nightly tests pass on cygwin. <ulp!>

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

Hi Marshall, LLVM *is* cool .. just not on cygwin! :) Sorry for the sad state of the cygwin build. I had hoped to have it cleaned up by now but many other things have been taking my time. Although the build has been succeeding in recent days, I'm not sure it will buy you anything. NONE of the nightly tests pass on cygwin. Until I can get some time to figure out why that is happening, I doubt

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

Hi, I'm looking into LLVM, and I must say it looks supremely cool. However, I'm having a hard time getting anywhere with it, since I don't have a linux machine here, and cygwin seems like a bit of a second-class citizen. The instructions to build the cygwin binaries are outdated, so I have to just make some guesses as to what the right thing to do is, and I'm apparently not

Hello Barry, Are you still using Cygwin? Why not try using MinGW instead. I think Cygwin cannot create .DLL files or if it can, the build scripts are not set up to do it from Cygwin. IIRC, Cygwin support is being dropped from later versions of LLVM so you'll have to either use Visual C++ to compile it or MinGW. See http://www.mingw.org for downloads. --Sam ----- Original Message ----

On Mon, 2004-09-13 at 22:38, Jeff Cohen wrote: > I don't know anything about Interix. > It may be best to defer a true Win32 port. It's not just the time it > would take to do it, it's the time to keep it up to date as LLVM > evolves. The Win32 port will constantly break, and I don't have the > time to keep fixing it. I've got my own time-consuming projects :)

I don't know anything about Interix. It may be best to defer a true Win32 port. It's not just the time it would take to do it, it's the time to keep it up to date as LLVM evolves. The Win32 port will constantly break, and I don't have the time to keep fixing it. I've got my own time-consuming projects :) That said, the architectural issues should still be addressed. What

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load

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

Is there a site doing current builds of Win32 binaries? Also, is there any project working in a non cygwin port of rsync? Thanks!

Jeff, These are all reasons why the Win32 port doesn't exist today. LLVM is heavily influenced and implemented by Unix tools/concepts/facilities. Since building on Win32 will also be a problem, I think that we should just target cygwin as our Win32 solution for now and get that to work really well. I know cygwin is a slow pig, but at least we can get LLVM to work with it. We also have Interix

I'd like to write a DLL wrapper (BladeEnc/lame_enc style) for libvorbis. I pulled down the CVS tree today, and with very slight changes (missing typedefs for int64_t, int16_t, etc...) got it to build using gcc 2.95.2 in Win95. Unfortunately, the encoder_example segfaults. I get the same results from Cygwin as well. On a linux box with egcs 2.91.66 it builds cleanly, and appears to

On 26 July 2010 04:35, Michael Spencer <bigcheesegs at gmail.com> wrote: > Attached is the 5th and final patch of the beginning of COFF support > for MC. It simply makes the X86 backend use it on Win32 targets and > tests it. > > You probably want to add Cygwin and MinGW32 Triples as well :- case Triple::Win32: + case Triple::Cygwin: + case Triple::MinGW32: return

Hi Has anybody ever tried (and most probably failed) to port rsync to Win32? I know there are versions built with cygwin and there are also other Windows programs that include the rsync algorithm. But neither of them make me really happy. The cygwin version is dead slow on my AMD 3500+ and the Windows programs all make something differently, can't be scripted and/or have an unusable GUI. I

Hi I found a small Bug when compiling OpenSSH under Win32 using Cygwin. When you use SSH as a interactive Shell everthing looks normal but when you try to transfer binary data via SSH you will get only garbage. Example: ssh -l root -i ./.ssh/identity server1 cat /tmp/test.tar.gz > c:\test.tar.gz The problem is that stdout is opend as Text-File so every LF which

On Mon, Jul 26, 2010 at 12:04 PM, Aaron Gray <aaronngray.lists at gmail.com> wrote: > You probably want to add Cygwin and MinGW32 Triples as well :- >    case Triple::Win32: > +  case Triple::Cygwin: > +  case Triple::MinGW32: >      return new WindowsX86AsmBackend (T); > Aaron Can someone test this on those platforms? That change would effect quite a few people. -

On Fri, 18 Feb 2005, Aaron Gray wrote: >>> I thought Whidbey would really be upto the job, obviously not. >> >> Well, we don't know until someone tries. > > Oh, well we have got a bug to report to Microsoft then ! > > I still may carry on implementing any mods on the VS2003 port over to 2005 > so we know where we are with that. There may well be a second

On Sat, 1 May 2004, Anthony Evans wrote: > I was wondering whether anyone has attempted to port LLVM to windows > running with a POSIX layer, such as cygwin? I know that Brian once got the LLVM CVS core compiled under Cygwin, but I don't recall how well it worked. I thought he had the JIT running, but I might be wrong. > I recently tried to build and run llvm on cygwin, and I got