Path: utzoo!attcan!uunet!ginosko!brutus.cs.uiuc.edu!usc!bloom-beacon!UMIACS.UMD.EDU!jsw
From: jsw@UMIACS.UMD.EDU
Newsgroups: comp.windows.x
Subject: Re: Problems building GNU Emacs with DECwindows
Message-ID: <8909130047.AA05734@lorax.umiacs.UMD.EDU>
Date: 13 Sep 89 00:47:20 GMT
References: <2684@orion.cf.uci.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 33


 > I'm trying to build GNU Emacs v18.55 on a DECstation 3100 running
 > Ultrix v3.0 and DECwindows.  When ld links the executable, it
 > complains that malloc, realloc and free are multiply defined.  ld does
 > leave a src/temacs file, which seems to run ok if I chmod it to have
 > execute permissions.  I then run make again and it builds the dumped
 > verions of Emacs, which also appears to run ok in the limited testing
 > I've done on it.

 > Has anyone else built GNU Emacs on a DECstation 3100 using the
 > DECwindows X11 library and gotten around this problem? 


I have had a similar problem with many X applications and DEC's version
of libX11.a .  I usually get a message that calloc is multiply defined.
I have been able to get around this message in the past by expressly 
specifying linking with libc.a right before libX11.a  

example:

	ld -o bozo foo.o bar.o -lc -lX11

I think this causes libc.a to be read twice, but, I get no warnings and the
executables have the correct permissions.


Why does DEC define calloc (and some other memory allocation funcs) in 
libX11.a ?  The libX11.a has malloc defined (external text) in XvmsAlloc.o
in libX11.a and calloc defined in XvmsCalloc.o in libX11.a ?  Are these
for VMS?

Jeff Webber /   U of Maryland Institute for Advanced Computer Studies
path: uunet!mimsy!jsw  phone (301)-454-7687  jsw@lorax.umiacs.umd.edu