Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!uflorida!ukma!rutgers!bellcore!faline!sword!yba
From: yba@sword.bellcore.com (Mark Levine)
Newsgroups: comp.windows.x
Subject: Re: Xman and fixes
Message-ID: <980@sword.bellcore.com>
Date: 7 Feb 89 16:37:20 GMT
References: <44248@linus.UUCP> <8902062012.AA23419@DORA.MIT.EDU>
Reply-To: yba@sword.bellcore.com.UUCP (Mark Levine)
Organization: Bellcore, Red Bank NJ
Lines: 20

For some reason I also had problems with installing the patches to
"xman".  It turns out that there were a large number of reject files
(*.rej) after the first attempt, which produced symptoms described by
the original poster (won't compile, lots of errors).  Perhaps this was
due to earlier problems with another fix, or we each had similar but
different problems.  In any case, I would recommend reinstalling the
application sources from the original sources, then applying only the
relavant patches again -- this fixed xman up for me.

[We need a way to stop the automatic -R option in patch in cases where
things go wrong; staying in sync when a patch is on its way in in half
the source files and on its way out in the other half gets tricky!
Read those output logs.... :-)]

In my case the actual cause was that we had increased the maximum
number of man pages per section (our section 3 was getting full because
we ended up with BOTH expanded and unexpanded names by using make
install and omitting the by-hand follow-up) so that one of the patch
hunks was rejected.  I guess using patch implies no local changes to
source code.