[Spread-users] compilation problem

Ryan Caudy caudy at jhu.edu
Mon Jul 7 10:29:12 EDT 2003


What platform (hardware/os) are you trying to compile for?

--Ryan

Koorosh.Alahiari at ubs.com wrote:

> Hi,
> 
> I have tried to install spread3.17.1 but get compilation problems when
> make builds memory .c 
> 
> cc -g -I. -I.   -DHAVE_CONFIG_H -c memory.c
> "memory.c", line 136: reference to static variable "Mem_Bytes_Allocated" in inline extern function
> "memory.c", line 140: reference to static variable "Mem_Obj_Inuse" in inline extern function
> "memory.c", line 144: reference to static variable "Mem_Obj_Allocated" in inline extern function
> "memory.c", line 148: reference to static variable "Mem_Max_Bytes" in inline extern function
> "memory.c", line 152: reference to static variable "Mem_Max_Obj_Inuse" in inline extern function
> "memory.c", line 156: reference to static variable "Mem_Max_Objects" in inline extern function
> "memory.c", line 160: reference to static variable "Mem" in inline extern function
> "memory.c", line 166: reference to static variable "Mem" in inline extern function
> "memory.c", line 170: reference to static variable "Mem" in inline extern function
> "memory.c", line 175: reference to static variable "Mem" in inline extern function
> "memory.c", line 179: reference to static variable "Mem" in inline extern function
> "memory.c", line 183: reference to static variable "Mem" in inline extern function
> "memory.c", line 187: reference to static variable "Mem" in inline extern function
> 
> =============================
> 
> What should I do to fix this?
> 
> Thanks K
> 
> Visit our website at http://www.ubs.com
> 
> This message contains confidential information and is intended only 
> for the individual named.  If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.  Please 
> notify the sender immediately by e-mail if you have received this 
> e-mail by mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free 
> as information could be intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain viruses.  The sender therefore 
> does not accept liability for any errors or omissions in the contents 
> of this message which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.  This 
> message is provided for informational purposes and should not be 
> construed as a solicitation or offer to buy or sell any securities or 
> related financial instruments.
> 
> 
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
> 

-- 
Ryan W. Caudy
Center for Networking and Distributed Systems
Department of Computer Science
Johns Hopkins University





More information about the Spread-users mailing list