[comp.mail.mh] mh on berkely 4.3 "Reno"

c3ar@zaphod.uchicago.edu (Walter C3arlip) (03/27/91)

Our sysop has recently upgraded our system to Berkeley 4.3 "Reno" (we are
running a vax).  Of course mh broke, and I have to get it working again for
myself and the few mh converts I've created.

Unfortunately, the batch fails.

Currently I'm stuck with the following problem: A program called m_gmsg.c
fails to compile and reports:
  /usr/bin/cc -DATHENA -DBSD42 -DBSD43 -DDUMB -DISI -DMORE='"/usr/bin/more"'
  -DBIND -DMHE -DMHRC -DOVERHEAD -DWHATNOW -DSENDMTS -DSPRINTFTYPE=int -O -c
  m_gmsg.c
  /usr/include/machine/machparam.h: 56: MSIZE redefined
  "m_gmsg.c", line 53: illegal function
  "m_gmsg.c", line 53: illegal function
  "m_gmsg.c", line 177: illegal function
  "m_gmsg.c", line 177: illegal function
   *** Error code 1
   Stop.

Yes, indeed, MSIZE seems to be defined both in machparam.h (as a constant)
and in mh.h.

Help! What do I do to get around this?

Thanks . . .

--Walter
_____________________________________________________________________________
Walter Carlip
(the "3" is invisible)                  **** carlip@ace.cs.ohiou.edu ****
_____________________________________________________________________________




_____________________________________________________________________________
Walter Carlip 		        	**** carlip@ace.cs.ohiou.edu ****
(the "3" is invisible)                   **** c3ar@finite.chi.il.us ****
_____________________________________________________________________________

jromine@buckaroo.ics.uci.edu (John Romine) (03/28/91)

c3ar@zaphod.uchicago.edu (Walter C3arlip) writes:
>  /usr/bin/cc -DATHENA -DBSD42 -DBSD43 -DDUMB -DISI -DMORE='"/usr/bin/more"'
>  -DBIND -DMHE -DMHRC -DOVERHEAD -DWHATNOW -DSENDMTS -DSPRINTFTYPE=int -O -c
>  m_gmsg.c
>  /usr/include/machine/machparam.h: 56: MSIZE redefined
>  "m_gmsg.c", line 53: illegal function
>  "m_gmsg.c", line 53: illegal function
>  "m_gmsg.c", line 177: illegal function
>  "m_gmsg.c", line 177: illegal function
>   *** Error code 1
>   Stop.
>Help! What do I do to get around this?

I would put "#undef MSIZE" just after the include of machparam.h.
--
John Romine