X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Sat, 25 May 2013 19:25:39 +0300 From: Eli Zaretskii Subject: Re: Adding 64-bit file support to DJGPP In-reply-to: <90dceebd-8d81-4433-8932-9bce42bddb97@googlegroups.com> X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83k3mnqb5o.fsf@gnu.org> References: <1137560452 DOT 398133 DOT 301490 AT g14g2000cwa DOT googlegroups DOT com> <0ed77a97-aec8-4fde-8124-707ca9cffad1 AT googlegroups DOT com> <28c2ff16-6cef-46c3-8f52-f67b320b5c04 AT googlegroups DOT com> <68c3dec5-8fd4-4eb0-888d-3949d879a33c AT googlegroups DOT com> <90dceebd-8d81-4433-8932-9bce42bddb97 AT googlegroups DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Sat, 25 May 2013 08:56:19 -0700 (PDT) > From: Georg Potthast > > As long as you do not access the hardware directly it is really easy to port a DJGPP program to MinGW. Did you actually try that? My experience in porting to MinGW is exactly the opposite: DJGPP has a lot of Posix-like features that MinGW sorely lacks. So porting to MinGW using a DJGPP port as a starting point will generally give you a broken port, and in many cases will simply refuse to compile or link. Besides, starting with DJGPP will automatically lose the advanced features you can have with Windows: networking, threads, parallel processes, etc. DJ's suggestion to use MinGW is still valid, of course (although MinGW still doesn't support generation of 64-bit executables; you need to go to semi-official MinGW64 snapshots). But please don't underestimate the efforts required for porting a non-trivial package to MinGW. Heck, even running a configure script is a challenge, and requires an installation of yet another environment (MSYS).