Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <001601c01574$d6afd0d0$92d698d1@hotrod>
From: shell AT shellware DOT com (Shell M. Shrader)
To: <cygwin AT sources DOT redhat DOT com>
Subject: RESOLVED: GCC 2.95.2 make problems under Cygwin 1.1.4
Date: Sun, 3 Sep 2000 03:01:47 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0013_01C01553.4CDDB140"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700

------=_NextPart_000_0013_01C01553.4CDDB140
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I was able to finally get GCC 2.95.2 make(ed) and installed under the =
Cygwin Net release on my Win2k machine but it wasn't without =
dificulties.

I had to modify two routines to get the make to succeed:  etime_.c and =
dtime_.c=20

etime_.c & dtime_.c both reference the HighPart and LowPart properties =
of the LONG_INTEGER datatype.  However, they nor any of their included =
modules #include winnt.h which is the only win32 header I could locate =
that defines this structure.

In both routines the HighPart and LowPart properties were being used to =
facilitate a hack for non NT win32 systems---
...
         LARGE_INTEGER freq;
...=20
 /* We need to use this hack on non-NT platforms, where the first call
    returns 0.0 and subsequent ones return the correct value. */
 if (win32_platform !=3D VER_PLATFORM_WIN32_NT)
   {
...
             clock_freq =3D ((unsigned long long) freq.HighPart << 32)
                          + ((unsigned) freq.LowPart);
...
     count =3D ((unsigned long long) counter_val.HighPart << 32)
             + (unsigned) counter_val.LowPart;
...

I opted to comment out the references to HighPart and LowPart and simply =
return a value of 1 in both routines because I'm on an NT system and =
could care less of the impact to non-NT systems as this is a localized =
installation.  I suspect the proper thing to do would be to #include =
winnt.h or track down the source of LARGE_INTEGER without including =
winnt.h but I was fearful that I would cause additional conflicts and =
I'm tired of messin' with the make.

Previously I had tried to use the GCC Cygwin patches to take care of the =
compiler warnings but gave up as they introduced incoherent FATALs =
within my Stage 1 build.  Guess I'll soon find out the impact of the =
multple compiler warnings I got.

Am I the only W2K gcc-2.95.2 / Cygwin 1.1.4 user out there to have this =
problem?  I find it very hard to believe that I'm the first W2K =
gcc-2.95.2 / Cygwin 1.1.4 user.

Shell


------=_NextPart_000_0013_01C01553.4CDDB140--