RFC: Cygwin 64 bit?

Corinna Vinschen corinna-cygwin@cygwin.com
Wed Jun 29 07:01:00 GMT 2011

On Jun 28 18:09, Daniel Colascione wrote:
> On 6/28/11 12:51 PM, Charles Wilson wrote:
> > Right, we have to decide -- my point is there isn't an easy answer that
> > will have zero impact on everybody.  There are basically three choices:
> > 
> >   /bin + /bin64 -- affects $PATH, implicates package naming (*). Also
> >                    might affect script #! lines, and anything that calls
> >                    exec*() or spawn() with a full pathname.
> So if I have a foo-32bit.exe in a directory that's not /bin or /bin64,
> it might segfault on startup depending on whether /bin or /bin64 comes
> first in $PATH? And whichever path is correct for foo-32bit.exe will be
> incorrect for foo-64bit.exe and vice versa?

Now that you mention it, yes, that would be the case if the DLLs have
the same name and are using the same "cyg" prefix.

Which kind of screams for another prefix for 64 bit DLLs.  Alternatively
for an entirely different way to load 64 bit DLLs.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-developers mailing list