2010/9/20 Earnie <ear...@users.sourceforge.net>:
> Cesar Strauss wrote:
>>
>> Since MSYS is derived from Cygwin, one way to get 64-bit support for
>> MSYS would be to add it first to Cygwin and port it to MSYS later.
>> However, as this thread indicates, there is currently some interest
>> on bringing 64-bit support to MSYS, while I do not have evidence
>> there is a similar interest on the Cygwin front. So, it may make
>> sense to do it the other way around this time (adding 64-bit support
>> to MSYS first and contributing back to Cygwin later).
>>
>
> I suggest that it would make more sense "the other way around". Since
> MinGW GCC is used for parts of the Cygwin/MSYS build process,
> incorporation of mingw-64 into Cygwin/MSYS would also need to take place.
>
> Earnie
Well, AFAIU this subject about porting msys (cygwin) to x64 requires
the following steps.
1.) Port the internal runtime-dll (sorry I am just knowing cygwin's
name here) cygwin1.dll. As this provides the syscalls required for any
later build.
2.) Port gcc/binutils to support the x86_64-*-cygwin* target. This
step shouldn't be too hard, but has for sure some pitfalls
3.) Best in parallel to 2.) Porting newlib beginning from headers.
After that real fun begins as all unix tools need to be ported to LLP64 ABI.
Regards,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
