Displaying 10 results from an estimated 10 matches for "internix".
Did you mean:
intermix
2004 Jul 07
1
[LLVMdev] AsmWriter.cpp:255: error: ambiguous overload for `std::basic_ostream<char,...
...that
>>>>can't
>>>>figure out which std::basic_ostream to use. Why?
>>>
>>>What I'm saying is that it appears that your implementation of operator<<
>>>is not functional or is missing. You said that you are using GCC on
>>>internix. Is it possible that when you configured/built gcc that it
>>>didn't find 64-bit integer support and disabled it or something?
>>>
>>>I really no nothing about internix so all I can do is speculate. Sorry.
>>>
>>>-Chris
>>>
>>>
&g...
2004 Jul 06
0
[LLVMdev] AsmWriter.cpp:255: error: ambiguous overload for `std::basic_ostream<char,...
...;
> As far as I can see, correct me if I'm wrong, it is the compiler, that can't
> figure out which std::basic_ostream to use. Why?
What I'm saying is that it appears that your implementation of operator<<
is not functional or is missing. You said that you are using GCC on
internix. Is it possible that when you configured/built gcc that it
didn't find 64-bit integer support and disabled it or something?
I really no nothing about internix so all I can do is speculate. Sorry.
-Chris
> > > Compiling AsmWriter.cpp
> > > AsmWriter.cpp: In function `voi...
2004 Jul 03
1
[LLVMdev] CommandLine.cpp:189: error: `strdup' undeclared
On Sat, 3 Jul 2004, Chris wrote:
>
>That should work fine. I'm not familiar at all with internix, but it
>appears to have a buggy header or something. From what I understand,
>internix is a posix layer for windows. Have you tried compiling under
>cygwin?
No, not yet.
>If you grab the latest CVS sources, they should work fine with
>cygwin, and will probably work better with w...
2004 Jul 06
2
[LLVMdev] AsmWriter.cpp:255: error: ambiguous overload for `std::basic_ostream<char,...
No, Chris, I'm not buying that argument, due to I've tweaked
/usr/include/types.h a little bit, so the configuration and compilation of
the cfrontend would be correct:
/*
* 64bit type for BSD compatability
*/
#ifdef __GNUC__
typedef long long int quad_t;
typedef unsigned long long int u_quad_t;
typedef long long int int64_t;
typedef unsigned long long int u_int64_t;
2004 Jul 03
1
[LLVMdev] CommandLine.cpp:189: error: `strdup' undeclared
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
2004 Jul 07
0
[LLVMdev] AsmWriter.cpp:255: error: ambiguous overload for `std::basic_ostream<char,...
...ong, it is the compiler, that
>>>can't
>>>figure out which std::basic_ostream to use. Why?
>>
>>What I'm saying is that it appears that your implementation of operator<<
>>is not functional or is missing. You said that you are using GCC on
>>internix. Is it possible that when you configured/built gcc that it
>>didn't find 64-bit integer support and disabled it or something?
>>
>>I really no nothing about internix so all I can do is speculate. Sorry.
>>
>>-Chris
>>
>>
>>
>>> > >...
2004 Jul 15
2
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)
>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 at the moment able to edit the file. Anyway, at this
moment, I don't know how to hack it, before I know more about autoconf. I'll
edit later when 1.3 is released.
Hi
I'v...
2004 Jul 14
1
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
>From: John Criswell <criswell at cs.uiuc.edu>
>Date: Wed, 14 Jul 2004 09:11:03 -0500
>
>
>The DataTypes.h header file is generated by the configure script and placed
>into your build tree. My best guess is that your system's header files do
>not correctly define these macros, so they are missing.
>
I did a search on the build and source trees, but neither
2004 Jul 14
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)
...e: Wed, 14 Jul 2004 14:49:01 -0500 (CDT)
>The file you need to modify is here:
>llvm/include/Support/DataTypes.h.in
>
>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 doesn't seem to be that advanced (due to
I'm porting LLVM 1.2). But, when I get one (nearby LLVM 1.3), I'll try to
broaden the scope, when I know how to modify .in configuration files.
However, I've found that the min and max values for...
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)
On Fri, 16 Jul 2004, Henrik Bach wrote:
> >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 at the moment able to edit the file. Anyway, at this
> moment, I don't know how to hack it, before I know more about autoconf. I'll
> edit later when 1.3...