🚀 go-pugleaf

I'm just now installing Epoch 3.2 here, and I caught only the tail end
of what seemed to be a discussion of the changes needed to get it
running on a DS3100 under Ultrix 3.1.  Could someone please send or
describe the necessary changes?  

I know about the need to change the null pointer test on line 99 of
xresource.c when DATA_SEG_BITS is defined, but this change does not
seem to be sufficient.

Using the m-pmax.h and s-bsd4-3.h, the make runs fine, though the
compiler generates a lot of warnings about the redefinition of
DATA_START, but compiles ok until "./temacs -batch -l inc-vers" hangs
with this backtrace:


>  0 make_uninit_string(length = 33) ["alloc.c":519, 0x44bb30]
   1 make_string(contents = 0x88bfe0 = "Warning: past 75% of memory
	   limit", length = 33) ["alloc.c":497, 0x44ba34]
   2 build_string(str = 0x88bfe0 = "Warning: past 75% of memory
	   limit") ["alloc.c":506, 0x44baa4] 
   3 malloc_warning(str = 0x88bfe0 = "Warning: past 75% of memory
	   limit") ["alloc.c":77, 0x44af38] 
   4 morecore(nu = 10) ["malloc.c":359, 0x4736a4]
   5 .block199 ["malloc.c":497, 0x473a64]
   6 malloc.malloc(n = 8184) ["malloc.c":497, 0x473a64]
   7 init_strings() ["alloc.c":458, 0x44b890]
   8 init_alloc_once() ["alloc.c":1427, 0x44d800]
   9 main(argc = 4, argv = 0x7fffeca4, envp = 0x7fffecb8)
	   ["emacs.c":377, 0x429264] 


In this configuration we have, from m-pmax.h,

#define DATA_START 0x10000000
#define DATA_SEG_BITS 0x10000000

and temacs seems to be hanging when init_strings() makes some
ridiculously large malloc request, triggering a warning that tries to
use the (not yet allocated) string space to compose its warning
message.

Anyway, I'd appreciate hearing how anyone who has gotten Epoch 3.2
working on a DS3100 did so...

Ed Rak
rak@gramian.harvard.edu