This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: RFC: Cygwin 64 bit?
On Jun 27 13:52, Andy Koppe wrote:
> On 27 June 2011 09:42, Corinna Vinschen wrote:
> > Maybe I misunderstood you? ÂI thought you meant that libncurses10 is
> > the last 32 bit version, libncurses11 is the first 64 bit version and
> > that's that.
> [...]
> The idea here is to support 32-bit only as far as needed to avoid
> having to port the whole distro to 64-bit from day one. Obviously this
> doesn't make sense if you don't want to relegate 32-bit to legacy
> status.
No chance to do that. 32 bit systems will exist for a long time yet.
There are still people buying a 32 bit W7 right now.
> > They don't have to. ÂThis suggestion is based on the assumption that
> > we will have 32 and 64 bit DLLs using the same name, and partially
> > even 32 and 64 bit tools using the same name.
>
> Of course. The point was that if no-one else does this, it's likely to
> cause Cygwin-specific challenges. I don't really know what I'm talking
> about here, but I think the basic issue would be install rules
> assuming that binaries go into /bin, which wouldn't work if the 64-bit
> DLLs are in /bin64.
That's indeed a problem which has to be solved in some way.
> > For instance, it would be most easy to keep the Cygwin 32bit package
> > as it is, with all the tools like mkpasswd, mount, getfacl, etc.
> > And the 64 bit package would look the same, just that it installs
> > into /bin64.
>
> With the scheme I outlined above, there could be a single 64-bit
> 'cygwin' package, version 2.x, much as it is now, plus a cygwin-legacy
> package (or some such name) with the 32-bit DLL(s) only.
Alternatively, we only have a single Cygwin package at all. It unpacks
a 32 bit DLL as well as a 64 bit DLL, as well as the 32 and 64 bit
utils, but only one set of headers. On all systems.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat