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: cygipc (and PostgreSQL) XP problem resolved! From: Robert Collins To: cygwin@cygwin.com In-Reply-To: <20030510072239.GA19367@cygbert.vinschen.de> References: <20030506174725.GE1652@tishler.net> <3EB84F52.3020608@ece.gatech.edu> <20030507133326.GA1824@tishler.net> <3EB9A54B.8060500@ece.gatech.edu> <20030508135217.GD512@tishler.net> <3EBB22F5.4000801@ece.gatech.edu> <1052541657.1675.5.camel@localhost> <3EBC8ED0.4040906@ece.gatech.edu> <20030510072239.GA19367@cygbert.vinschen.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BBWS3g5XH3+Mwj3h2QK1" Organization: Message-Id: <1052554219.1824.14.camel@localhost> Mime-Version: 1.0 Date: 10 May 2003 18:10:19 +1000 --=-BBWS3g5XH3+Mwj3h2QK1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable key_t, as it's used for ipc, is likely to be *problematic* to transition in a 'fat binary' style. You'd need a 32 bit set of key creation routines, and and translation table to lookup 32bit keys in the list of 64 bit keys .... Given that cygipc is *not* in cygwin today, and you'd be adding it, I'd simply have it 64 bit from the first release uploaded to sources. And I'd time that for oh, a day after cygwin 1.5 goes up as a testing package. (And release cygipc as testing whilst cygwin 1.5 stays in testing). Rob --=20 GPG key available at: . --=-BBWS3g5XH3+Mwj3h2QK1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+vLPqI5+kQ8LJcoIRApkFAJ9uOnI3oG0JteJ4BO1u8OPq55KfTACg1hQn 6X4V/QZ0mBJUhOukHm6f79U= =jQHM -----END PGP SIGNATURE----- --=-BBWS3g5XH3+Mwj3h2QK1--