Okay, finally decided to give in and hack the OS-supplied signal.h. I put the
sigset_t def in-line where the extern ref was. make then choked on swig because
of - you guessed it - multiple defs for sigset_t. I then removed swig from the
configure line but it still chokes on swig? (Even did make extraclean.) Anyway,
the svn binary was compiled; I have no swig (so no viewsvn), but at least I've
Thanks for your help - been a decade or so since I've done any real C/C++... I
would like to know the root cause, though, others have not had this problem on
Solaris 2.8 using same apache2/subversion versions. My Solaris box recently had
patches applied, but maybe it still isn't completey patched up? Or is this
possibly an issue with the subversion build process?
--- phLi <firstname.lastname@example.org> wrote:
> Hrmz, the .i file (cancel.i) doesn't have a definition for sigset_t? I guess
> the earlier output from --trace-includes doesn't mean that
> /usr/include/sys/signal.h was properly included then?
> --- "Martin_v._L÷wis" <email@example.com> wrote:
> > phLi wrote:
> > > Thanks for your responses. sigset_t is defined in
> > > which is included at the beginning of /usr/include/signal.h. The
> > is
> > > not conditional. Using --trace-includes yields this output which I assume
> > means
> > > the definition is included properly:
> > I see. Please invoke gcc with --save-temps, and inspect the resulting .i
> > file for the definition of sigset_t; please report that definition.
> > > So, I guess you are telling me gcc gives a "parse error" when it can't
> > a
> > > type def?
> > That's the typical cause, yes. It thinks sigset_t is a plain identifier,
> > and not a typename, making "sigset_t *" a syntax error (because you
> > can't have a plain identifier followed by an asterisk in a parameter list).
> > Regards,
> > Martin
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri May 2 22:33:26 2003