Add the -m32 option for the Linux x64 target to the linker-flags.
Fix for a segfault, caused by writing to static memory in a signal handler.

How to reproduce the segfault: it can be reproduced on a Linux x64 build, by following these steps:
1) Start the interpreter (by itself, or by gdb if you want some additional information).
2) Press Ctrl-C
3) ==>The '[escape]' text will appear.
4) Press Enter.
5) ==>The interpreter crashes.

Here is an example reproduction with some debugging information about the segfault:

a) Starting a debugging session:
$ gdb ./r3
>>>>>(gdb) r
>>>>>Starting program: /home/delian/Work/r3/make/r3
......
b) Press Ctrl-C to switch to the debugger, and emulate the signal which the r3 process will receive on a normal Ctrl-C:
>>>>>(gdb) signal SIGINT
>>>>>Continuing with signal SIGINT.
>>>>>[escape]
c) Here simply press 'Enter'
>>Program received signal SIGSEGV, Segmentation fault.
>>0x080b2aa6 in Fetch_Buf () at ../src/os/host-stdio.c:101
>>101             Std_IO_Req.data[len] = 0;
>>(gdb) bt
>>#0  0x080b2aa6 in Fetch_Buf () at ../src/os/host-stdio.c:101
>>#1  0x080b2b52 in Get_Str () at ../src/os/host-stdio.c:147
>>#2  0x080b1c09 in main (argc=1, argv=0xffffcf54) at ../src/os/host-main.c:183

After the fix is applied, the 'Std_IO_Req.data[len] = 0' line will write to a fresh heap copy of the static string instead of the static string itself, thus avoiding the segfault.

I've tried to pass a global array to avoid the copy, but then the string '[escape]' becomes corrupted to '[' after the first Ctrl-C, and subsequently it shows just '[' if you press it again.
Merge pull request #13 from spytheman/fix_m32_linker_flags

Add the -m32 option for the Linux x64 target to the linker-flags.
Updated system object license reference
Merge pull request #20 from spytheman/fix_segfault_on_SIGINT

Fix for a segfault, caused by writing to static memory in a signal handler
start on Visual Studio nmake makefile
build all
Merge pull request #24 from kjk/vc-build

Visual Studio build system
fix for possible crash in do-callback native function
fix for APPEND_BYTES in crash messages
adding baseline .gitignore - still to be expanded for r3
updated .gitignore for R3 related non-repository files
Merge pull request #27 from earl/fix-lvalue-required-error

Fix GCC compiler error: "lvalue required as increment operand"
Don't use 'thread' declspec on MinGW
Default to standalone binary build, for now

For Win32, this builds the host objects without having the libr3
functions marked as dllimport. This fixes linking the standalone
binary.

On the other hand, this breaks linking a host-only binary. For that
to work, we'll probably need separate object dirs to hold objs built
for standalone or host-only.
Don't explicitly link to libc

The MinGW compiler barks on this.
Explicitly link against wsock32 and comdlg32 for win32 builds

Otherwise MinGW complains.
Build OS-specific host files based on systems parameters

Instead of always only building the os/posix/ set of host files.
Build Win32 binaries with the GUI flag
Raise the stack size to 4MiB for Win32 binaries

On Win32, the stack size is a property of the PE binary. The R3 core lib
currently assumes a default stack size of 4MiB, but the Win32 build with
MinGW built binaries with 1MiB stack size.

This fix adjusts the build system parameters to create Win32 binaries
with 4MiB stack size, matching the R3 core lib default assumption.

This fixes CC1732: http://issue.cc/r3/1732