Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #43914
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Another Gforth snapshot |
| Date | 2015-11-28 22:11 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <n3d55e$9tl$1@dont-email.me> (permalink) |
| References | <mrgah4$11j$1@dont-email.me> <6e377f1d-4e4c-4a6e-8c67-68bec93644d4@googlegroups.com> |
mhx@iae.nl wrote:
> On Tuesday, August 25, 2015 at 1:50:38 AM UTC+2, Bernd Paysan wrote:
>> In the usual place, date code 20150825:
>>
>> https://www.complang.tuwien.ac.at/forth/gforth/Snapshots/
> [..]
>> Please report back if that works.
>
> (I have a full cygwin64 install that is good enough to compile and
> run even X-windows.)
>
> When using the self-installing Windows binary a DOS window opens and
> I see at least four error messages.
Ok, I see the problem: launching 64 bit sh.exe from 32 bit programs (PE32)
doesn't work anymore. Since the setup.exe installer is a PE32 program,
installing gforth64 won't work. The error messages look like this:
fork: can't reserve memory for parent stack 0x600000 – 0x800000, (child has
0x400000 – 0x600000), Win32 error 487
Since this affects the older gforth64 installers, too, it's probably not a
new Cygwin64 bug, but a new Windows bug. Tested with Windows 10 1511.
From a quick look it seems that installing a 32 bit sh.exe in {app}\..\bin
fixes the problem; this 32 bit sh.exe needs its own set of cygwin dlls
(fortunately they can stay in {app}\..\bin, and won't conflict with Gforth's
directory), and it can launch 64 bit Gforth during install successfully.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ*
http://bernd-paysan.de/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-25 01:50 +0200
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-25 02:12 +0200
Re: Another Gforth snapshot peter.m.falth@gmail.com - 2015-08-25 13:57 -0700
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-26 01:46 +0200
Re: Another Gforth snapshot peter.m.falth@gmail.com - 2015-08-25 23:56 -0700
Re: Another Gforth snapshot mhx@iae.nl - 2015-08-26 00:49 -0700
Re: Another Gforth snapshot anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-08-26 07:57 +0000
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-26 15:26 +0200
Re: Another Gforth snapshot anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-08-26 16:04 +0000
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-27 01:18 +0200
Re: Another Gforth snapshot Greg <borota@gmail.com> - 2015-08-25 20:20 -0700
Re: Another Gforth snapshot anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-08-26 09:03 +0000
Re: Another Gforth snapshot Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-08-27 11:29 +0100
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-27 15:17 +0200
Re: Another Gforth snapshot Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-08-27 19:54 +0100
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-28 04:06 +0200
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-08-28 04:16 +0200
Re: Another Gforth snapshot mhx@iae.nl - 2015-11-28 03:12 -0800
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-28 17:23 +0100
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-28 22:11 +0100
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-29 01:00 +0100
Re: Another Gforth snapshot mhx@iae.nl - 2015-11-28 17:11 -0800
Re: Another Gforth snapshot Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-29 03:07 +0100
csiph-web