Correct. The StaticAssert macro is used to introduce compile-time assertions into the code. The reported errors comes from static assertions that fail, i.e., something is not satisfying the assumptions that the remaining code depends on, and it's visible at compile time, so we abort compilation with the StaticAssertion<false> failure.
The solution is to make the assumptions true again. /L On Sun, Jan 9, 2011 at 11:17, Stephan Beal <[email protected]> wrote: > On Sun, Jan 9, 2011 at 2:28 AM, misham <[email protected]> wrote: > >> src/objects-inl.h:2873: error: invalid application of 'sizeof' to >> incomplete type 'StaticAssertion<false>' >> > > StaticAssertion<false> does not appear to be defined anywhere. This might > be intentional, and is probably a sign that your build triggered a static > assertion set up by the v8 developers. > > step...@ludo:~/src/google/v8/src$ grep 'StaticAssertion<' * > checks.h:template <> class StaticAssertion<true> { }; > checks.h: > StaticAssertionHelper<sizeof(StaticAssertion<static_cast<bool>(test)>)> \ > step...@ludo:~/src/google/v8/src$ cd ../include/ > step...@ludo:~/src/google/v8/include$ grep 'StaticAssertion<' * > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- Lasse R.H. Nielsen [email protected] 'Faith without judgement merely degrades the spirit divine' Google Denmark ApS - Frederiksborggade 20B, 1 sal - 1360 København K - Denmark - CVR nr. 28 86 69 84 -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
