similar to: [LLVMdev] lib/System Unleashed - Need Your Help!

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>

Folks, With some MacOS help from Nate, I've begun the conversion of LLVM to use lib/System, the operating system independence layer. Currently, the library has implementations for three abstractions: Path, Program, and Signals. These provide some basic utilities for manipulating file system paths, finding and executing programs, and cleaning up after Signals. The implementations should work

Hi Reid, > With some MacOS help from Nate, I've begun the conversion of LLVM to use > lib/System, the operating system independence layer. Currently, the > library has implementations for three abstractions: Path, Program, and > Signals. Did you consider using boost::filesystem for Path abstraction? See the documentation on: http://boost.org/libs/filesystem/doc/index.htm

Hi Vladimir, The LLVM source base used to be dependent on boost but we have removed that dependency because it had a high cost for the relatively small portions of it that we needed. boost is a general purpose C++ library that happens to handle filesystem things in a somewhat portable way. However, lib/System will handle signals, memory mapped files, program execution, and several other things

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

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

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

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

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

Reid Spencer wrote: > Folks, > > With some MacOS help from Nate, I've begun the conversion of LLVM to use > lib/System, the operating system independence layer. FYI, I'm getting this on an up-to-date tree: Compiling Path.cpp In file included from platform/Path.cpp:20, from Path.cpp:37: platform/../Unix/Path.cpp: In static member function `static

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

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

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: Before the patch: 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

Hi By manipulating a #define for G++ I've managed to compile int64_t type with ostream. Now, I'm stopped by some to me unknown constants: ----------------------------------- Compiling Constants.cpp Constants.cpp: In static member function `static bool llvm::ConstantSInt::isValueValidForType(const llvm::Type*, long long int)': Constants.cpp:368: error: `INT8_MAX' undeclared

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

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]

>From: Chris Lattner <sabre at nondot.org> >Date: Wed, 14 Jul 2004 14:49:01 -0500 (CDT) > >There is currently support for building in non-cygwin windows environments >protected by _MSC_VER. You just need to broaden the scope of the #ifndef >to include internix. > Sorry Chris, but my DataTypes.h.in seems to be outdated (due to I'm porting LLVM 1.2), so I'm not