Displaying 4 results from an estimated 4 matches for "400bytes".
Did you mean:
400kbytes
2008 Dec 05
2
[LLVMdev] Build errors on trunk for about a week now.
...char *,
_Ty=unsigned int,
_Pr=`anonymous-namespace'::StrCmp
]
Allocator.cpp
APSInt.cpp
I cannot really look at it well since the termserv connection is
effectively less then modem speed, but I looked at Annotation.cpp from
the svn (also not fun, downloading at ~400bytes a second), but from a
quick look-see, I would bet that on line 34, changing:
bool operator()(const char *a, const char *b) {
To:
bool operator()(const char *a, const char *b) const {
Will fix that error. Which makes sense, all functor adapters for the
STL things like map are supposed to be...
2008 Dec 05
0
[LLVMdev] Build errors on trunk for about a week now.
OvermindDL1 a écrit :
> Been trying to build the trunk to test some things for about a week
> now using VS8 (VS2k5). Tons of Warnings (like things first being
> declared struct, being redefined class and so forth, those need to be
> fixed, but are otherwise not harmful), and a *lot* of errors. Being
> trunk I figured just the normal trunk-type issues, but it has been
> going on
2008 Dec 05
0
[LLVMdev] Build errors on trunk for about a week now.
...,
> _Pr=`anonymous-namespace'::StrCmp
> ]
> Allocator.cpp
> APSInt.cpp
>
> I cannot really look at it well since the termserv connection is
> effectively less then modem speed, but I looked at Annotation.cpp from
> the svn (also not fun, downloading at ~400bytes a second), but from a
> quick look-see, I would bet that on line 34, changing:
> bool operator()(const char *a, const char *b) {
> To:
> bool operator()(const char *a, const char *b) const {
> Will fix that error. Which makes sense, all functor adapters for the
> STL things...
2008 Dec 05
2
[LLVMdev] Build errors on trunk for about a week now.
Been trying to build the trunk to test some things for about a week
now using VS8 (VS2k5). Tons of Warnings (like things first being
declared struct, being redefined class and so forth, those need to be
fixed, but are otherwise not harmful), and a *lot* of errors. Being
trunk I figured just the normal trunk-type issues, but it has been
going on for a while now, so figured it would be good to