Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!uxc.cso.uiuc.edu!garcon!pequod.cso.uiuc.edu!dorner
From: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Newsgroups: comp.sys.next
Subject: Re: wall's patch program on NeXT
Message-ID: <1560@garcon.cso.uiuc.edu>
Date: 25 Jul 89 18:05:49 GMT
References: <55970@tut.cis.ohio-state.edu>
Sender: news@garcon.cso.uiuc.edu
Reply-To: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Organization: University of Illinois at Urbana-Champaign
Lines: 28

In article <55970@tut.cis.ohio-state.edu> amra@cis.ohio-state.edu (Nasir K Amra) writes:
>
>	I've tried to compile wall's patch program on a NeXT machine,
>but whenever, I ran the Configure shell script it bombs out on trying
>to figure out if cpp can run to accept standard input. 
>	Have anyone managed to get the program running?


Yes.  The problem is that it uses this for a test:

#define ABC abc
#define XYZ xyz
ABC.XYZ

and looks for "abc.xyz" in the output.  Well, gnu's cpp produces "abc .xyz".
I changed Configure to use:

#define ABC abc
ABC

and to look for "abc" in the output, and Configure is happy.  I don't know
if anybody is out there writing code that depends on the behavior of
the preprocessor when stringing symbols together; if so, it ain't going
to work on the NeXT.
-- 
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu  UUCP: {convex,uunet}!uiucuxc!dorner
IfUMust:  (217) 244-1765