Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: gary@svx.sv.dg.com
Newsgroups: comp.sys.sun
Subject: Re: Using make to compile for sun3 and sun4
Keywords: SunOS
Message-ID: <131@brazos.Rice.edu>
Date: 12 Jul 89 08:17:54 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 71, message 3 of 18

In article <4226@kalliope.rice.edu> Kemp@dockmaster.ncsc.mil writes:
>X-Sun-Spots-Digest: Volume 8, Issue 60, message 4 of 7
>After watching the "make wars" on info-unix between GNU make and AT&T
>toolchest make, I am convinced that we Sun users have a pretty good
>product that has lots of good features that were added without breaking
>compatibility or introducing lots of bugs.

Until you try to port, e.g., xtroff to your 4.0.x system and discover that
make got broken in 4.x for targets with 2 or more "."s in the name.

Having just tried to explain "yacc stack overflow" while porting c++ to the
Sun software rep, I can't wait to try this one on them ---
"Could you send us an example of the code that causes the yacc stack overflow?"
"Why?"
...
"Could you send us some targets with multiple "."s in them..."
-- 
Gary Bridgewater, Data General Corp., Sunnyvale Ca.
gary@sv4.ceo.sv.dg.com or 
{amdahl,aeras,amdcad,mas1,matra3}!dgcad.SV.DG.COM!gary
No good deed goes unpunished.