[coyotos-dev] build error

[Charles Landau]

At 9:40 AM -0400 6/19/07, Jonathan S. Shapiro wrote:
>On Mon, 2007-06-18 at 14:51 -0700, Charles Landau wrote:
>>  At 3:46 PM -0400 6/18/07, Jonathan S. Shapiro wrote:
>>  >On Mon, 2007-06-18 at 11:37 -0700, Charles Landau wrote:
>>  >>  make[4]: Entering directory `/home/clandau/coyotos/src/base/idl'
>>  >>  capidl: frontend/SymTab.cxx:99: static void
>>  >>  Symbol::PushScope(sherpa::GCPtr<Symbol>): Assertion
>>  >>  `!Symbol::CurScope || newScope->nameSpace == Symbol::CurScope' failed.
>>  >>  make[4]: *** [BUILD/h/coyotos/builder.h] Aborted
>>  >
>>  >We haven't tried to keep EROS capidl up to date, because we have no way
>>  >to test it. To handle this error, I'm going to need to know how to
>>  >reproduce it.
>>  >
>>  >Happy to look, but can you provide instructions?
>>
>>  I was intending to build for Coyotos, not EROS or CapROS. I just
>>  followed the instruction at coyotos.org: run "make" in coyotos/src.
>>
>>  I don't think there's anything in my shell environment variables that
>>  would cause a problem. (Ambient state is almost as bad as ambient
>>  authority.)
>>
>>  I sync'ed the Coyotos source a few days ago.
>>
>>  What other information can I give you?
>
>How about the input IDL? Or at least a call stack? This error is not an
>environment error. It is an error in the symbol management logic. It may
>mean that the input is invalid, but it more likely means that you are
>exercising a case we haven't hit yet. There is little chance of
>resolving this sort of error without input to reproduce the problem.

The input is from your coyotos source:
coyotos/src/base/idl/builder.idl

>For example, do you know which input file you were processing?
>
>Also, having updated libsherpa, have you done a fully clean build? You
>can do this by:
>
>   cd coyotos/src
>   make distclean
>   make

Did that - same error, on the second make command.

The failing command was:
../../ccs/capidl/BUILD/capidl -I. -I/home/clandau/coyotos/usr/idl -D 
BUILD/h -l c-header builder.idl