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

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: Thu, 16 Sep 2004 13:26:09 -0700 > >Okay, so the question is, how do you do the equivalent of a MAP_ANON >allocation on Interix. We don't want to map a file here. We're just asking >for virtual memory (unbacked by swap or file) to be allocated to the >process. Is there a way to do that on Interix? The

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: 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

Hi Reid, I downloaded the latest source code and ran configure (I suppose it was that you did mean). The result is: --------------- checking build system type... i586-pc-interix3 --------------- Otherwise, please correct me. /Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- >From: Reid Spencer <reid at x10sys.com>

Hi Interix does not know MAP_ANON or -NOCORE only MAP_SHARED, -PRIVATE and -FIXED. Henrik _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Memory.cpp.zip Type: application/x-zip-compressed Size: 495 bytes Desc: not

I would like to volunteer for the port of Interix and Win32 platforms, if no one objects against this. /Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- >From: Reid Spencer <reid at x10sys.com> >Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >To: LLVMdev List <llvmdev at cs.uiuc.edu>

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

> >> >>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 development team) have >supplied their own header files to support the win32 API. > To be exact, I use mingws own header

Hi > >Are you able to explain below meaning to me? > >#if defined(_ALL_SOURCE) \ > || (defined(_XOPEN_SOURCE) && (_XOPEN_SOURCE_EXTENDED==1)) \ > || (__STDC__ - 0 == 0 && !defined(_POSIX_C_SOURCE)) >extern char* __cdecl strdup(const char *); >#endif /* defined(_XOPEN_SOURCE) && (_XOPEN_SOURCE_EXTENDED == 1) */ > (RTFM) Some of the above

Hi Guys I'm trying to port and build LLVM to the Interix environment. I've succeded until the Interix version of gcc program executes: gmake[1]: Entering directory `/usr/local/src/llvm/lib/Support' gmake[1]: Leaving directory `/usr/local/src/llvm/lib/Support' gmake[1]: Entering directory `/usr/local/src/llvm/lib/Support' Compiling CommandLine.cpp CommandLine.cpp: In function

Hi >From: Chris Lattner <sabre at nondot.org> >Date: Thu, 15 Jul 2004 17:43:27 -0500 (CDT) >Ah, suddenly everything makes sense. If you're interested in LLVM on the >windows platform, *please* get CVS. Last night I've got the latest version of LLVM from CVS and now porting LLVM to Interix from this version on. I got this error: --------------------- gmake[1]:

Hi Brian Here's the config.log (I'm not posting it on the dev-list). The automatic gcc macro for Interix is __INTERIX if this is to any help. /Henrik >From: "Brian R. Gaeke" <gaeke at uiuc.edu> >Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >Subject: Re: [LLVMdev]

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

Reid, >As for Interix support in general, I'm having a hard time determining >which variant of Unix Interix implements. It seems to be partially Posix >1 and partially Posix 2 based. Do you have any further information >related to the specific standards supported by Interix? I don't want to >incorrectly categorize the Interix support. I've discussed this subject with

Hi John, Please see below, too >From: John Criswell <criswell at cs.uiuc.edu> >Date: Tue, 27 Jul 2004 14:57:02 -0500 > >Henrik Bach wrote: >>Hi, > >Please see below. > >> >>I get this error: >>------------------ >>ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >>ToolRunner.cpp:396: error: (Each

>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

Reid, >Well, if it doesn't break anything else, I'd fix the header file. The >standard type name is supposed to uint64_t not u_int64_t. I would just >change the header file to define both of them, something like: > >typedef u_int64_t uint64_t; > >You could do that in /usr/include/types.h, I've tried it and it doesn't break anything, but ... >or we could

Hi again Does cygwin support shared libraries. And if not, how did you port llvm on this issue? /Henrik >From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Tue, 27 Jul 2004 00:41:53 +0200 > >Hi, > >I get this error: >------------------ >ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >ToolRunner.cpp:396:

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. On the other hand, no one has submitted any Win32 patches yet, so first come first served :) Reid. On Mon, 2004-09-13 at 19:35, Jeff Cohen wrote: > Uh... shouldn't a Win32 port use