RE: [OpenJade-devel] Errors trying to get OpenJade 1.4 to compileagain

[Richard S. <sh...@ns...>]

At 08:17 AM 4/25/01 +0200, Nilsson, Peter wrote:
>> -----Original Message-----
>> From: Richard Sharpe [mailto:sh...@ns...]
>> Subject: [OpenJade-devel] Errors trying to get OpenJade 1.4 to compile
>> again
>> 
>> OK, I have checked some more things out, and tried to fix 
>> what looked like
>> a bad include directive, but that yields the same result ...
>> 
>What include line?

OK, I noticed that there was no -I/usr/local/include/OpenSP in any of the
compile steps, so I added that via a command to the make, but I get exactly
the same error.

>> Looks like I am going to have to brush up on my C++ ...
>
>Probably holds for me too (see below), even though I'm using that language
>every workday...

What I meant by this is: Learn C++ :-)

>> Here are the problems from the log file:
>> 
>> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../grove -g -O2
>> -Wp,-MD,.deps/GroveBuilder.pp -c GroveBuilder.cxx  -fPIC -DPIC -o
>> .libs/GroveBuilder.lo
>> GroveBuilder.cxx:307: warning: `class OpenSP::GroveImpl' only 
>> defines a 
>> private destructor and has no friends
>
>Just to clarify. This is an old warning (has been there as long as I've been
>using Jade). GroveImpl is reference-counted and destroys itself when the
>count goes to zero. So this is OK.

Yes, I figured that this was a warning that I could ignore for now.

>> GroveBuilder.cxx: In method `OpenJade_Grove::AccessResult 
>> OpenSP::PrologPiChunk::getFirstSibling (const OpenSP::GroveImpl *, 
>> const OpenSP::Chunk *&) const':
>> GroveBuilder.cxx:74: `struct OpenSP::Chunk' is inaccessible
>> GroveBuilder.cxx:660: within this context
>...
>
>Chunk is inaccessible as a base class (since PrologPiChunk derives from
>PiChunk (public), PiChunk derives from CharsChunk (private)). But it isn't
>accessible as a class delcared in namespace scope, so I don't know if the
>compiler is correct don't accounting for that. Maybe
>typedef SP_NAMESPACE_SCOPE Chunk Chunk;
>in the PrologPiChunk could help. Otherwise you could always change the
>inheritance, but that's not really clean... If you find a solution that
>looks strange (as the above), please comment on it in the code until we know
>if the compiler or the code is buggy.

This is all Spanish to me ... That is, I can only half understand what you
are saying ...

Thank you any way for the feedback, and I will have to look at it some
more, I guess ...

>Regards,
>//Peter


Regards
-------
Richard Sharpe, sh...@ns...
Samba (Team member, www.samba.org), Ethereal (Team member, www.ethereal.com)
Contributing author, SAMS Teach Yourself Samba in 24 Hours
Author, Special Edition, Using Samba