On 17/03/2013 16:45, Christopher Faylor wrote:
> I'd like to have a feel for how the 64-bit version of Cygwin will
> impact package maintainers.
>
> So, I'd appreciate some discussion about this.
>
> 1) Do you have a 64-bit version of Windows available?
Yes.
> 3) Are you willing to download the current 64-bit Cygwin and start porting
> your stuff, knowing that there are still bugs?
>
> 4) Or, would you rather wait for 64-bit to be completely stable before
> attempting anything?
I don't have to wait for it to be completely stable but it'll be a few weeks
before I'm able to get up to speed and figure out what's going on.
> 5) Does the existence of two different architectures make you think that
> it is time for you to stop offering the package?
Nope.
> 6) Would you be willing to have another person doing the 64-bit port for
> you?
>
> 7) Are you ok with a 64-bit alpha release being made available which contains
> your packages built by someone else?
I don't have any ego issues about it, but don't know what would be involved
in this. Is it just a matter of rebuilding with recent cygport? I think I
could be able to do that in reasonably short order.
On a related issue, I don't see anything related to cygwin64 in upstream
GCC. How is 64-bit Cygwin currently being built? Are you using a mingw64
compiler and controlling things like startup files and libs linked against in
the command-line?
(Sorry for being so behind the times. I've got an ~20k backlog of emails
between Cygwin, binutils and GCC.)
cheers,
DaveK
