SCRIPT? string fix (http://issue.cc/r3/1885)
Robustness fixes to SAVE

Fixes http://issue.cc/r3/1907 and http://issue.cc/r3/1908 - ported from
rebol-patches.
Make sure line endings are normalized to LF

We need a .gitignore file to make sure that line endings get normalized
to LF. My last two commits got distorted because of this - they were
very small changes that are showing up as big changes because of the
line ending change. Same goes for the draw.r and shape.r files which I
didn't change at all.
Add make-make for creating new makefiles. Fix objs directory problem.
At least on a current OS X,  (llvm-)gcc defaults to 64-bit, which breaks Rebol struct alignment. Force 32-bit build and link.
Fix clean
- clean should remove objs directory, otherwise subsequent builds will fail.
- use -f to suppress warning for missing libr3.so
Fixed whitespace.
Merge pull request #1 from rebol/master

Catching up
Merge pull request #1 from BrianHawley/master

Mezzanine fixes from rebol-patches
Merge pull request #3 from juhagman/b-osx-build-fix

OS X build fix
Fix for existing objs dir
Add -m32 to Linux 4.4 build options
Fix a couple typos.
Add the -m32 option for the Linux x64 target to the linker-flags.
fixed GCC compiler error: "lvalue required as increment operand"
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