X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Received: by 10.107.28.67 with SMTP id c64mr2882393ioc.1.1445363577736; Tue, 20 Oct 2015 10:52:57 -0700 (PDT) X-Received: by 10.182.116.130 with SMTP id jw2mr66915obb.4.1445363577698; Tue, 20 Oct 2015 10:52:57 -0700 (PDT) Newsgroups: comp.os.msdos.djgpp Date: Tue, 20 Oct 2015 10:52:57 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse AT google DOT com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=134.3.44.91; posting-account=OsAajgoAAADdKJnkJkmhzqP0jo6I_P_0 NNTP-Posting-Host: 134.3.44.91 References: <5611566C DOT 4020507 AT iki DOT fi> <561A4BCE DOT 7050606 AT iki DOT fi> <56213FE2 DOT 7090409 AT iki DOT fi> <562168C6 DOT 5050001 AT gmx DOT de> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Random compile errors under WIndows (32 bit Windows Vista and Windows 10) From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" Injection-Date: Tue, 20 Oct 2015 17:52:57 +0000 Content-Type: text/plain; charset=ISO-8859-1 Bytes: 3972 Lines: 62 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp 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 On Monday, October 19, 2015 at 8:26:54 PM UTC+2, Wiktor S. wrote: > > AFAIK Microsoft has clearly state that they are no longer interested in > > suporting MS-DOS applications on their OSs. > > And all DJGPP programs are MS-DOS applications that require a full > > functional > > DOS environment to work flawlessly, so IMO it becomes very unlikely that > > the > > goal of getting DJGPP working on modern Windows operating systems can ever > > be > > achived. I am not opposing on trying to get DJGPP working on Windows 10 > > or > > similar OS but in consideration of the fact of the small amount of DJGPP > > users > > and the even smaller amount of skilled DJGPP developers really familiar > > with > > DJGPP internals and Windows internals, this will take at least a couple of > > months > > more, probably it will take years. IMO, an attempt to get DJGPP working > > on > > Windows 10 or similar operating systems shall be postponed until 205 has > > been > > released. The over the years vanishing group of DJGPP users do not > > deserve to > > wait until the end of days for this release. I really think that we shall > > take > > seriously user questions like this one: > > > It's obvious that MS has no intention to bring NTVDM back to its glory. > But sticking to Windows XP as the "last good OS" is as slow path to death of > DJGPP. > If there is to be any future of DJGPP (a very limited one, but still a > future), the project has to embrace what is still alive: DOSBox and FreeDOS. > Full compatibility may require a cooperation with those projects' > developers, and fixing some things on their sides too, but at least those > *can* be fixed, unlike Windows. > > A mid-term goal should be a successful build of DJGPP/gcc/binutils on > FreeDOS (as I understand it doesn't work right now). > > > > -- > Wiktor S. I think that no one denies that with Vista DJGPP has reached the end of the road on Microsoft operating systems. Only for the record: with the 2.05 release it is possible to compile the repository code without any difficulties. On MSDOS-6.22 with DOSLFN 0.41c it took around 7 hours. On FreeDOS 1.0 (not FreeDOS 1.1) without LFN driver it tooks 3:39 hours. Every thing else will become really difficult due to different issues in FreeDOS and other issues in certain DJGPP ports. May be there are also issues in libc.a itself. I do not know if every code snippet committed to the repository has really been checked to work on MS-DOS too instead. I doubt that the vast majority of the developers still have access to some MS-DOS version. Regards, Juan M. Guerrero