Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: trying again - cpan/gcc cannot compile perl module after cygwin 1.5* From: Robert Collins To: Brian.Kelly@Empireblue.com Cc: cygwin@cygwin.com In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BAXMnGVoJzkfmreWOxbX" Message-Id: <1068936348.1109.202.camel@localhost> Mime-Version: 1.0 Date: Sun, 16 Nov 2003 09:45:48 +1100 --=-BAXMnGVoJzkfmreWOxbX Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2003-11-16 at 09:41, Brian.Kelly@Empireblue.com wrote: > Of course I'm aware that cygwin is now *64* bit compiled, and that I'm > looking to compile a *32* bit module. So I guess my first question, is > there backward compatibilty? And, if there is, how can I invoke it for > successful compilation? Also - any hope that the default installation wil= l > ever again compile this, or is there now a need for a Win64::Semaphore > module? Huh? Win32 !=3D the 32 in cygwin that has been changed to 64. Win32 is a published set of API's from MS. the 32 bit limitation cygwin has was for file offsets and similar typedefs. Why not just just walk through the erroring bits and see whats going on. My WAG is that they used incorrect typedefs. Rob --=20 GPG key available at: . --=-BAXMnGVoJzkfmreWOxbX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQA/tqybI5+kQ8LJcoIRAgmcAJ44MUlXJQOiaaDa0nKktXlIahi17wCfbp25 iPGiCa+i53fhjzhLgrNR8GQ= =zTC0 -----END PGP SIGNATURE----- --=-BAXMnGVoJzkfmreWOxbX--