From d9336f91aad7b09c7315fe5794c2514e91d11e54 Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Fri, 13 Feb 2015 23:51:18 -0500 Subject: TinyFugue works on Yosemite. --- wiki/muds/tinyfugue-on-yosemite.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 wiki/muds/tinyfugue-on-yosemite.md (limited to 'wiki/muds/tinyfugue-on-yosemite.md') diff --git a/wiki/muds/tinyfugue-on-yosemite.md b/wiki/muds/tinyfugue-on-yosemite.md new file mode 100644 index 0000000..1754436 --- /dev/null +++ b/wiki/muds/tinyfugue-on-yosemite.md @@ -0,0 +1,21 @@ +# Compiling TinyFugue on Yosemite + +TinyFugue's site claims that it works on OS X. This is largely true, but the +switch from `gcc` to `clang` has eliminated support for some _deeply_ legacy +symbols. + +Since SourceForge is a death zone, I'll post my fix here. To get TinyFugue to +compile, apply the following patch: + + --- src/malloc.c.orig 2015-02-13 23:45:44.000000000 -0500 + +++ src/malloc.c 2015-02-13 23:45:28.000000000 -0500 + @@ -12,7 +12,6 @@ + #include "signals.h" + #include "malloc.h" + + -caddr_t mmalloc_base = NULL; + int low_memory_warning = 0; + static char *reserve = NULL; + +This symbol appears to be unused. Certainly I haven't been able to find any +references, and `tf` works well enough. -- cgit v1.2.3