I had similar problems building on gcc 2.96. I ended up having to take the optimizations out of the compile options (the -O2 flag) and everything worked fine after that.
-----Original Message----- From: Joseph Laccone [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 10:32 AM To: [email protected] Subject: Re: Build Problems I am running gcc ver 2.96 OS is Linux (Kernel 2.4.9-e.49) > This is a multipart message in MIME format. > > What version of gcc and OS level are you building on? > > June K. Ng > XSLT Development > Email: [EMAIL PROTECTED] > > > > > "Joseph Laccone" <[EMAIL PROTECTED]> > 02/07/2005 10:57 AM > Please respond to > xalan-c-users > > > To > [email protected] > cc > > Subject > Build Problems > > > > > > > I am having problems building Xalan 1.9 on my website. Xerces built > fine and is running. > > Here is the error I receive. > > g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX - > D_REENTRANT -DXALAN_INMEM_MSG_LOADER -c -I/usr/local/xml- xalan/c/src - > I/usr/local/xml-xalan/c/include -I../../nls/include - > I/usr/local/xerces-c-src_2_6_0/src/ -I/usr/local/xerces-c- > src_2_6_0/include/xercesc -I/usr/local/xerces-c-src_2_6_0/include/ - > o ../../obj/XalanDOMString.o /usr/local/xml- > xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp > > Cannot allocate 2109696 bytes after allocating 8616924 bytes > make[1]: *** [../../obj/XalanDOMString.o] Error 1 > make[1]: Leaving directory `/usr/local/xml-xalan/c/src/xalanc' > make: *** [all] Error 2 > > Can anybody tell me what is causing this (and how to fix it)? > > Joe > > > ----- The Bearded One http://www.beardboy.org ********************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system. Thank You.
