[comp.sources.bugs] bug with Configure in elm 2.3

kak@hico2.UUCP (Kris A. Kugel) (08/19/90)

for some reason, when I run the Config script,
it doesn't set the VOIDSIG flag right in config.h:


/* VOIDSIG:
 *	This symbol is defined if this system declares "void (*signal())()" in
 *	signal.h.  The old way was to declare it as "int (*signal())()".  It
 *	is up to the package author to declare things correctly based on the
 *	symbol.
 */
#	VOIDSIG 	/**/

Looks to me like somehow the undef got waylaid.

I couldn't find anything special about the d_voidsig flag in
the Configure script, and I'm not willing to spend the time
right now to investigate to it further.

I am running using ksh on a 3b1 (alias unixpc, alias 7300).

I am not currently receiving this newsgroup, so any reply should
be sent by e-mail:
                               Kris A. Kugel
                              (201) 842-2707
       {uunet,att,rutgers}!westmark!hico2!kak  <--well-connected
		    {tsdiag,ka2qhd}!hico2!kak  <--frequent
{ssbn,zorch,zinn,ditka,daver,attdso}!hico2!kak <--every two days

PS. I suspect that the "use Reply/To" option in the config scrip should
alway be NO if you don't have a smart mailer or pathalias and aren't
next to major nodes.

syd@DSI.COM (Syd Weinstein) (08/21/90)

kak@hico2.UUCP (Kris A. Kugel) writes:

>for some reason, when I run the Config script,
>it doesn't set the VOIDSIG flag right in config.h:
This was a problem in ordering the lines and fixed early on in the
patches to 2.3.  Current version of Elm is 2.3PL6.

See the README file for how to get patches.
-- 
=====================================================================
Sydney S. Weinstein, CDP, CCP                   Elm Coordinator
Datacomp Systems, Inc.                          Voice: (215) 947-9900
syd@DSI.COM or dsinc!syd                        FAX:   (215) 938-0235