similar to: [LLVMdev] Files to lib/System/Win32

On Wed, 15 Sep 2004 19:28:26 +0200 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > >>I did successfully compile all those files with VC++ 7.1. Does mingw > >>come with it's own version of windows.h or are you using the official > >>Microsoft header files? > >> > > > >Due to legal issues with Microsoft, they (mingw

On Wed, 15 Sep 2004, Jeff Cohen wrote: > Anyway, I avoided bleeding edge stuff like WOW64 for now. Still, > Signals.cpp is going to require some esoteric Structured Exception > Handling stuff and debug symbol table support. Nothing that hasn't been > around for a while, but rarely used by the typical Windows programmer. Note that you don't HAVE to implement the stack trace

>From: Reid Spencer <reid at x10sys.com> >Date: Mon, 13 Sep 2004 21:07:16 -0700 > >Henrik, > >The patches you submitted will not work (at all) for the Win32 platform >because they (still) use Unix system calls. Win32 doesn't have mkdtemp, >fork, execve, etc. Furthermore in Path.cpp forward slashes are still >used. These need to be changed to back slashes. >

Uh... shouldn't a Win32 port use the Win32 API? On Tue, 14 Sep 2004 02:11:51 +0200 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > Hi > > Here is my first patches to the Win32 platform. > > They compile on the mingw platform. > > I haven't test them yet, but I thought it will best to put them in the save, > just in case... > >

Hi Here is my first patches to the Win32 platform. They compile on the mingw platform. I haven't test them yet, but I thought it will best to put them in the save, just in case... /Henrik _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/ -------------- next part -------------- An embedded and

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 13 Sep 2004 21:24:47 -0700 > > >But there are some issues with System I'm going to have to take care of >besides using Win32. There appears to be some Unix assumptions like the >presence of /etc or the HOME environment variable. Neither have any >true equivalent in Windows. > Will be fixed in a working

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Wed, 15 Sep 2004 10:35:36 -0700 > >What's a "compiling mesh?" What I meant, was that there are some implicit defines in mingw (like __GCC) and vcX (like _MVC) but possibly also other unsupported? internal structures. As I stated earlier mingw should be win32 api compliant, but not for complicating matters. But

Hi, I get this error: --------------- configure: configuring in projects/Stacker configure: running /bin/sh '/C/projects/src/llvm-2/llvm/projects/Stacker/configure' --prefix=/C/LLVM/tools/ '--prefix=/C/LLVM/tools/' 'CPPFLAGS=-D__MINGW -DLLVM_ON_WIN32=1' --cache-file=/dev/null --srcdir=/C/projects/src/llvm-2/llvm/projects/Stacker configure: error: invalid variable

Henrik, The patches you submitted will not work (at all) for the Win32 platform because they (still) use Unix system calls. Win32 doesn't have mkdtemp, fork, execve, etc. Furthermore in Path.cpp forward slashes are still used. These need to be changed to back slashes. So, I'm not familiar with mingw platform. Since you've stated they compile on your mingw platform, I'm assuming

>From: Reid Spencer <reid at x10sys.com> >Date: Mon, 13 Sep 2004 20:54:57 -0700 > >Yes, it should. I haven't reviewed Henrik's change set yet but if it >doesn't look like clean Win32 code then I will create a separate target >named MingW and adjust the configure script accordingly. > I've looked up in the VC and win32 api documentation, and it is truely

>From: Jeff Cohen <jeffc at jolt-lang.org> > >Uh... shouldn't a Win32 port use the Win32 API? > Well, as I see it LLVM contains only tools that are perfectably manageble through a shell. And in this respect, I see the win32/mingw port perfectably achieves this at the moment. >On Tue, 14 Sep 2004 02:11:51 +0200 >"Henrik Bach" <henrik_bach_llvm at

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 13 Sep 2004 21:29:34 -0700 > > >Actually, this is one thing that does not need to be done. Windows is >quite happy using forward slashes in Win32 APIs. Of course, any path >you get /back/ from Windows will have back slashes. I didn't notice this nice little feature :) > >But you do have to take drive

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Tue, 14 Sep 2004 07:25:11 -0700 > >On Tue, 14 Sep 2004 12:46:31 +0200 >"Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > > > >From: Jeff Cohen <jeffc at jolt-lang.org> > > >Date: Mon, 13 Sep 2004 21:24:47 -0700 > > > > > > > > >But there are some

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Wed, 15 Sep 2004 10:44:08 -0700 > >It's not hard in the sense that MSDN has sample code that does this. >It's not much more than cut and paste. But I could make it compile >conditionally so that it will compile only with Microsoft's compiler. > Leave it open as an excise. I'll barf if it's necessary

============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ =============================================================

Hi Jeff, _HEAPOK is unknown to mingw 1.0 (which is the official release). Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

Hi, This minor patch clarify matters in the CFEBuildInstrs.html file in my view. Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

Hi, Today I've succeded in compiling the llvm-tools, llvm-gcc and stacker frontend and in installing it. Uptill now I've followed the steps given in: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html with modifications for the mingw platform. I'll return with step-by-step instructions how to do it on this platform. Cheers Henrik :)

Yes, Chris you're right. It seems that my << operator for int64_t is missing in my '/opt/gcc.3.3/include/c++/3.3/bits/ostream.tcc' file. Which ordinary version of GCC are you working with and how do your definition of the << operator for int64_t look like? /Henrik > >Here is an excerpt from the config.log for LLVM: > >configure:19451: checking for int64_t

Here is an excerpt from the config.log: configure:19451: checking for int64_t configure:19476: gcc -c -g -O2 conftest.c >&5 configure:19479: $? = 0 configure:19482: test -s conftest.o configure:19485: $? = 0 configure:19496: result: yes configure:19511: checking for uint64_t configure:19536: gcc -c -g -O2 conftest.c >&5 configure:19539: $? = 0 configure:19542: test -s conftest.o