Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Wed, 22 Nov 2000 16:35:43 -0800 (PST)
From: Carlos Puig <cpuig AT home DOT com>
X-Sender:  <cpuig AT c445745-a DOT stcla1 DOT sfba DOT home DOT com>
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
cc: <cygwin-apps AT cygwin DOT com>
Subject: Re: Texinfo-4.0
In-Reply-To: <3A1C3784.9DEF7B94@ece.gatech.edu>
Message-ID: <Pine.LNX.4.30.0011221627240.10273-100000@c445745-a.stcla1.sfba.home.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 22 Nov 2000, Charles Wilson wrote:

> Carlos Puig wrote:
> >
> > Note: One small patch is needed to make texinfo-4.0 under cygwin.  On line 106
> > of the generated makeinfo/Makefile, add -DWIN32 as follows:
> >

> AArrrrggghhh!!!  No.  Don't rely on -DWIN32 -- it often turns on too
> many windows specific hacks, and leads to huge troubles later on.
> Cygwin is not windows.  What you should do, is inspect every .h and .c
> file, looking for '#ifdef WIN32'.

Ok, I looked at the entire source tree (using grep -r on my Linux
system) and found only two changes that depend on WIN32.  Both changes
are in makeinfo/files.c.  One of the changes (or equivalent) is
essential -- you can't even finish a make without it -- and the other
one is not.  So, implementing your suggestion requires patching two
lines in files.c.  I would be glad to generate the patch file, if there
is someone to recive it.

I'm looking for some guidance on how texinfo-4.0 (suitably patched)
could be included in cygwin releases to replace texinfo-3.12.  Is there
someone who normally handles packages like texinfo?  Are there formal
procedures I should follow?  (I'm new to this list.)

Thanks for your help.

Carlos