From: "Tom Demmer" <DEMMER AT brain1 DOT lstm DOT ruhr-uni-bochum DOT de>
Organization:  Lehrstuhl Stroemungsmechanik, RUB
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Date:          Wed, 15 Oct 1997 13:53:30 GMT-1
MIME-Version:  1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject:       Re: ANNOUNCE: libc patch site
Reply-to: Demmer AT LStM DOT Ruhr-Uni-Bochum DOT De
Message-ID: <61D2E1876F9@brain1.lstm.ruhr-uni-bochum.de>
Precedence: bulk

> On Tue, 14 Oct 1997, Thomas Demmer wrote:
> 
> > and install the sources under /djgpp/src.
> > unzip the required patchfile.
> > Type
> >  patch < ptfXXXX.pat
> 
> I suggest saying "patch -p0 < ptfXXXX.pat" instead.  Most of the patch
> files won't work automatically otherwise (you'll get a prompt from
> `patch' asking which file to patch).
> 
> > Make a context diff against the old stock source. Put this into 
> > ptfXXXX.pat, where the XXXX is replaced by the bug number. 
> 
> For those who don't know: context diffs are generated by the `diff'
> program (from GNU Diffutils, get v2gnu/dif271b.zip), with this
> command:
> 
>     diff -c old new
> or
>     diff -u old new
> 
> (-c and -u generate the diffs in different formats, but `patch'
> understands both; the output of -c is somewhat larger.)
> 
> But the important thing is TO PUT THE OLD VERSION FIRST on the command
> line!  Otherwise, your diff will be backwards.

Yes, but patch is smart enough to realize that the file either has 
been patched already, or if it should make a reverse patch. In case 
you know what you are doing, this can save your day. Most people 
don't, most of the time (including me, when trying this stuff)

> > The path should start relative to /djgpp/src.
> 
> I suggest to make it relative to the root of the DJGPP installation.
> That is how DJ Delorie asks the patches to be done.  If the same rule
> is preserved on this site, people won't need to create their patches
> twice.

Yes OK, I change that. With that, the ``-p0'' is required (Otherwise 
it is not)

> 
> Please use RELATIVE pathnames of the sources when you type the `diff'
> command line.  This will allow anybody to apply the patch
> automatically, even if their top-level DJGPP directory is different.
> 
> For example, here's how to create a patch for the `read.c' module:
> 
>  cd c:\djgpp
>  diff -c src/libc/posix/unistd/read.bak src/libc/posix/unistd/read.c > read.pat
> 
> (this assumes that DJGPP is installed in C:\DJGPP).
> 

That's what I intended to say in the paragraph above, except that I 
wanted it relative to libc. But you are completely right, it should 
be relative to src to be the start at the same place for _ALL_ 
libraries. 

And, to emphasize the topic again, make diffs against the stock 
source, i.e what comes out of djgpp/v2/djlsr201.zip. Otherwise, we'll 
soon be in trouble. 

I finally managed to compile libm (there were a few setnel to be 
replaced by setneb), so I hope it'll be available 
tomorrow morning. I'm not sure if a debuggable libm makes sense, but 
anyway. I'm not deep enough into mathmatics to have an idea what's 
going on, but that's probably not required. 

Anyway, there have been a few downloads since yesterday, I just lack 
the patches ;-)

Ciao
Tom

  ******************************************************************
  *  Thomas Demmer                     * Phone : +49 234 700 6434  *
  *  Universitaetsstr. 150             * Fax   : +49 234 709 4162  *
  *  Lehrstuhl fuer Stroemungsmechanik *                           *
  *  D-44780 Bochum                    *                           *
  ******************************************************************
  *  Email: demmer AT LStM DOT Ruhr-Uni-Bochum DOT De                         *
  *  WWW:   http://www.lstm.ruhr-uni-bochum.de/~demmer             *
  ******************************************************************

  Eighty percent of air pollution comes from plants and trees
                          --- Ronald Reagan, famous movie star