similar to: [LLVMdev] Type uint64_t required but not found

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, I get below error: --------------------------------- In file included from /usr/local/build/llvm/lib/System/platform/Path.cpp:23, from /usr/local/src/llvm/lib/System/Path.cpp:27: /usr/local/build/llvm/lib/System/platform/../Unix/Path.cpp: In member function `bool llvm::sys::Path::create_directory(bool)': /usr/local/build/llvm/lib/System/platform/../Unix/Path.cpp:343:

Hi, I get this error: ------------------ ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) ToolRunner.cpp:396: error: (Each undeclared identifier is reported only once for each function it appears in.) ------------------ And the config.log shows that configure has detected that ld on my platform (Interix) doesn't support shared libraries: ------------------

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:

Reid, >From: Reid Spencer <reid at x10sys.com> >Date: Tue, 31 Aug 2004 11:08:37 -0700 > >Henrik, > >Since Interix is POSIX and SUS compatible, I've separated its Another posting on Interix forum, has revealed that Interix conforms to POSIX.1 and SUS. But, I don't think this will break your platform separation. /Henrik

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 As shown below, the .\configure script found a version of stat.h: --------------------- configure:4382: checking for sys/stat.h configure:4399: gcc -c -g -O2 conftest.c >&5 configure:4402: $? = 0 configure:4405: test -s conftest.o configure:4408: $? = 0 configure:4419: result: yes --------------------- However, I got this error when compiling: --------------------- FileUtilities.cpp:

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>

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, or we could add it to a header file in llvm/include/Config, ifdef'd for Interix. Reid. On Tue, 2004-08-31 at

Hi Chris >From: Chris Lattner <sabre at nondot.org> >Date: Fri, 13 Aug 2004 16:23:53 -0500 (CDT) > >On Fri, 13 Aug 2004, Henrik Bach wrote: > > > I got this error: > > ------------------------------- > > gmake[3]: Entering directory `/usr/local/src/llvm/lib/Target/X86' > > Building X86.td register information header with tblgen > > tblgen:

Hi Can someone tell me, which files you get in the confstat* directory, when running: ./config.status -d /Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- _________________________________________________________________ Opret en gratis Hotmail-konto http://www.hotmail.com med udsigt til 250 MB lagerkapacitet

Hi I've started to port LLVM to the MinGW Win32 platform. To successfully recognize the platform, following statements should be inserted into the configure script: ---------- Index: configure ================================================================== RCS file: /var/cvs/llvm/llvm/configure,v retrieving revision 1.114 diff -u -r1.114 configure --- configure 7 Sep 2004 18:04:45 -0000

Hi I'm compiling: /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp on MinGW. However, it stops complaining about that SIGALRM is undeclared: -------------------------- @ /usr/local/build/llvm/mklib --tag=disable-shared --silent --tag=CXX --mode=compile g++ -c -I/usr/local/build/llvm/lib/Support -I/usr/local/src/llvm/lib/Support -I/usr/local/build/llvm/include

Yes, that's my understanding, too. But I'm not controlling where my library -ldbghelp is put when g++ is called. I just put it in the TOOLLINKOPTS variable in Makefile.config. Henrik >From: Reid Spencer <reid at x10sys.com> > >John Criswell wrote: >> >>It seems that the -L path options are specified before the LLVM libraries >>(libSystem and

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

Henrik Bach wrote: > Hi > > I'm compiling: /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp > on MinGW. However, it stops complaining about that SIGALRM is undeclared: Is there an alarm() syscall on MinGW? And if so, what signal does it send (according to the MinGW docs)? -- John T. > -------------------------- > @ /usr/local/build/llvm/mklib

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 30 Aug 2004 21:46:42 -0700 >FileParser.tab.c: In function `int Fileparse()': >FileParser.tab.c:2043: error: syntax error before `goto' > >The offending lines bison generated are: > >/*----------------------------------------------------. >| yyerrlab1 -- error raised explicitly by an action. |

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Tue, 14 Sep 2004 19:43:34 -0700 > >OK, I stand corrected: mingw can be used to create honest-to-goodness >Windows applications using Win32. But you're still using it as a Unix >emulator :) > OK, if POSIX.1 is unix emulation then we have that all *nix emulates all *nix and that's fine with me :) OK, I admit,

>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 TableGen/Record.cpp needs an include to DataTypes.h to compile correct on MinGW platform. Win32/Signals.cpp should test on define __MING instead of __MINGW_H. My fault. Henrik _________________________________________________________________ Opret en gratis Hotmail-konto http://www.hotmail.com med udsigt til 250 MB lagerkapacitet -------------- next part -------------- A non-text