On Thu, 17 May 2001, Gilles Detillieux wrote:
> Date: Thu, 17 May 2001 10:55:09 -0500 (CDT)
> From: Gilles Detillieux <[EMAIL PROTECTED]>
> To: Joe R. Jah <[EMAIL PROTECTED]>
> Cc: Gilles Detillieux <[EMAIL PROTECTED]>,
"ht://Dig mailing list" <[EMAIL PROTECTED]>
> Subject: Re: [htdig] Segfault on url_rewrite_rules
>
> According to Joe R. Jah:
> > Thank you Gilles; I used the "gmake LOCAL_DEFINES=-DHAVE_SYS_WAIT_H." It
> > compiled without a hitch, and digs just fine;) To make your patch work
> > universally, however, I'd need to follow your advice and pick up a C/C++
> > guide, to test which one of /usr/include/wait.h or /usr/include/sys/wait.h
> > exist, and have the correct definition inserted in include/htconfig.h or
> > Makefile.config. I made a shortcut and defined them both in
> > include/htconfig.h, but it failed; it looks for /usr/include/wait.h
> > regardless of the order of definitions in include/htconfig.h;(
>
> The order of the definitions doesn't matter. You're defining two
> different symbols, so one will have no effect on the other. If you
> look at the code in the patched ExternalParser.cc you'll see how
> they're used. If HAVE_WAIT_H is defined, it will include <wait.h>.
> Otherwise, if HAVE_SYS_WAIT_H is defined, it will include <sys/wait.h>.
> If they're both defined, it still only attempts to include wait.h because
> the ordering of the #ifdef's gives HAVE_WAIT_H precedence.
>
> It's important that you only define a HAVE_* or HAVE_*_H macro if you
> actually do have the corresponding function or header file. Normally this
> is all handled by autoconf, but I didn't have the fixes for this when
> I put together the ExternalParser.2 patch.
>
> Figuring out manually which header files you have is no big mystery!
> Just use the ls command to see what you have. E.g.:
>
> ls -l /usr/include/wait.h /usr/include/sys/wait.h
>
> I wasn't recommending the C/C++ guide for figuring out autoconf and
> automake. I suggested it because in your earlier e-mail you didn't
> seem to know how to define a C macro. This is pretty fundamental stuff.
> Maybe I misunderstood the question, and what you really meant to ask is
> how to define them *automatically*.
Thanks Gilles; I have ordered the book David recommended; I believe it
will be helpful.
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah [EMAIL PROTECTED]
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
