X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "neozeed (neozeed AT superglobalmegacorp DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Death of DJGPP support on Win10 32 bit? [WAS: Re: Max value of
 DpmiLimit registry setting in Windows 10 32 bit]
Date: Sat, 14 Apr 2018 18:44:47 +0800
Organization: Qemu OS/2
Lines: 41
Message-ID: <20180414-104447.99.0@neozeed.news.eternal-september.org>
References: <xnd0zpwjtr DOT fsf AT delorie DOT com> <c5ddafe3-5a20-79eb-bd9b-1794470021e9 AT iki DOT fi>
 <83sh8c47ey DOT fsf AT gnu DOT org> <e8a9925b-8ed9-9542-51bb-7c153f9573eb AT iki DOT fi>
 <83r2nw44a6 DOT fsf AT gnu DOT org> <20180406-091036 DOT 863 DOT 0 AT neozeed DOT news DOT eternal-september DOT org>
 <b2ce25f9-6861-4a46-8fb9-c0aedd99bf4a AT googlegroups DOT com> <CAA2C=vC0Bydw2gijQMKaUcKyaWGZXFgdB+vvN5GQR5MrQtEQzw AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
Content-Transfer-Encoding: 7Bit
Injection-Info: reader02.eternal-september.org; posting-host="7e40678a69ac4c40bcbab31600a2cde7";
	logging-data="10627"; mail-complaints-to="abuse AT eternal-september DOT org";	posting-account="U2FsdGVkX1/6QlOoZybIN/5TBkGxKJl9"
X-Newsreader: WinVN 0.99.16.0 (x86 64bit)
Cancel-Lock: sha1:LFGusRcp+iGrlYN6MHhzteZbHnk=
Bytes: 3395
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In article <CAA2C=vC0Bydw2gijQMKaUcKyaWGZXFgdB
+vvN5GQR5MrQtEQzw AT mail DOT gmail DOT com>, djgpp AT delorie DOT com says...
>On 4/10/18, rugxulo AT gmail DOT com [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com> 
wrote:
>> Hi,
>>
>> On Friday, April 6, 2018 at 4:10:41 AM UTC-5, neozeed wrote:
>>>
>>> If the NTVDM can't nest properly, isn't it easier to just use
>>> a Win32 native version of GCC, and keep your CC1/CPP/GAS/LD native?
>>
>> (I think I misunderstood this comment the first few times that I read 
it.)
>>
>> So you're saying use a Win32 (PE/COFF) gcc.exe as frontend with other
>> .EXEs remaining DJGPP (DOS, MZ/COFF)?
>
>I think he means a canadian-cross. i.e. run natively on win32 or
>win64 with all tools being win32/or win64 exes, and target djgpp.
>E.g.: https://github.com/andrewwutw/build-djgpp.git

For my own use, I wanted to get gcc 2.7.2.1 & binutils 2.8.1 running as a 
cross to build ancient MAME / Allegro, I had some issues doing a standard 
cross compile setup, but I dwas able to find the source fragment setup, and 
re-build them first under DOSBox, then go back on the makefile, and use 
MinGW to re-build the source behind the 'native' build, giving me a tool 
chain that was able to deal with Allegro's specific macros & asm, and being 
able to compile things like doom in under 2 seconds...

For the purist I'd just make the only things that are really needed to be 
native, native, in this case gcc.exe and possible cpp.exe to handle the long 
file names.  You can use the MS-DOS Player, to not only run MS-DOS / DJGPP 
exe's under Win64, this way, but MS-DOS Player can wrap them so that they 
can be simply invoked like any other exe.  On 32bit machines, CC1/GAS/LD 
ought to work as they did before, allowing these componets to remain 
'native', or via something like MS-DOS PLayer.

http://takeda-toshiya.my.coocan.jp/msdos/

I guess my larger point is that all hope is not necessarily lost.