You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-users@xalan.apache.org by Sa...@blr.hexaware.com on 2005/06/20 12:30:06 UTC

Fw: Xalan 64 bit issues with runConfigure - compile and link flags for the execreation

Hi Folks
I am new to this list.
I have fixed the Xalan 64 bit using GCC on SUN8, by mofifying the 
Makefile.incl.in .

How do we incoporate this into future releases on Xalan?

warm regards

Saurabh
----- Forwarded by Saurabh Bhatnagar/BLR/HTL on 06/20/2005 03:56 PM -----

"Jesse Pelton" <js...@PKC.com> 
06/17/2005 06:58 PM
Please respond to
c-dev@xerces.apache.org


To
<c-...@xerces.apache.org>
cc

Subject
RE: Xalan 64 bit issues with runConfigure - compile and link flags for the 
execreation






Since this is about building Xalan, you should post to the Xalan-C list
(see http://xml.apache.org/mail.html#xalan-c-users).  Among other
things, this ensures that others with similar questions can benefit from
your discoveries by searching the appropriate mailing list archive.  Of
course, you'll also get the benefit of responses from people who know
something about Xalan.  Most important, if changes to Xalan are required
to make it build with 64 bits, someone on that list is likely to be able
to commit the changes.  (They'll probably suggest that a bug report with
a patch attached is the ideal way to make things happen).

> -----Original Message-----
> From: Saurabh.Bhatnagar@blr.hexaware.com 
> [mailto:Saurabh.Bhatnagar@blr.hexaware.com] 
> Sent: Friday, June 17, 2005 6:34 AM
> To: c-dev@xerces.apache.org
> Cc: Leanid.Nazdrynau@oracle.com; Akshya.Pradhan@blr.hexaware.com
> Subject: Re: Xalan 64 bit issues with runConfigure - compile 
> and link flags for the execreation
> 
> Another update!
> 
> I was able to build Xalan 64 bit using runConfigure !!!
> 
> The problem was in $LINK and MAKE_SHARED_LOC commands being used by 
> Makefiles.
> 
> I have changed Makefile.incl.in by  modifying
> 
> #=============== SOLARIS SPECIFIC OPTIONS =========================
> Adding {LDFLAGS} to LINK under
> 
> For g++ specific options
> 
>         MAKE_SHARED = ${CXX} $(CXXFLAGS) -D${PLATFORM} -shared -fPI
> 
>         LINK = ${CXX} -D${PLATFORM} -fPIC ${LDFLAGS}
> 
>         ALLLIBS = ${LIBS} -L/usr/lib -L/usr/local/lib -lc
> 
> Also,  added this line for building  XalanMsgLib
> 
>         MAKE_SHARED_LOC = ${CXX} -D${PLATFORM} -shared -fPIC 
> ${LDFLAGS}
> 
> and moved the existing 
>     MAKE_SHARED_LOC = ${CXX} -D${PLATFORM} -G -ptr$(ALL_OBJECTS_DIR) 
> ${LDFLAGS} -h ${LOC_SONAME}
> 
> into SUN native compiler options.
> 
> 
> It's building fine.
> 
> Do you think we can add this to the future releases of 
> Makefile.incl.in ? 
> If so I will be happy to provide my changes.
> 
> 
> warm regards
> Saurabh
> 
> 
> 
> 
> Saurabh.Bhatnagar@blr.hexaware.com 
> 06/17/2005 11:42 AM
> Please respond to
> c-dev@xerces.apache.org
> 
> 
> To
> c-dev@xerces.apache.org
> cc
> 
> Subject
> Xalan 64 bit issues with runConfigure - compile and link 
> flags for the 
> execreation
> 
> 
> 
> 
> 
> 
> Hi,
> 
> Using the Xerces 64 bit I am building Xalan 64 bit.
> 
> runConfigure is not setting  the compile and link flags for the exe 
> creation like for MsgCreator, testXSLT and Xalan itself.
> How do I set them?
> 
> Output of runConfigure for the command line : 
>                                                 runConfigure 
> -psolaris 
> -cgcc -xg++ -b64 -z-m64 -l-m64 -P/user/sbhatnag/xalanv1.9_64
> 
> Generating makefiles with the following options ...
> Platform: solaris
> C Compiler: gcc
> C++ Compiler: g++
> Extra compile options:  -m64
> Extra link options:  -m64
> Transcoder: default
> Localization system: inmem
> Locale: en_US
> Thread option: 
> bitsToBuild option: 64
> Extra configure options:  --prefix=/user/sbhatnag/xalanv1.9_64
> Debug is OFF
> 
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking for a BSD-compatible install... ./install-sh -c
> checking for autoconf... true
> checking whether -fno-elide-constructors works correctly... yes
> checking build system type... sparc-sun-solaris2.8
> checking host system type... sparc-sun-solaris2.8
> checking for floor in -lm... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for egrep... grep -E
> checking for ANSI C header files... no
> checking for mbstowcs... yes
> checking if mbstowcs can count only... no
> configure: creating ./config.status
> config.status: creating Makefile.incl
> config.status: creating Makefile
> config.status: creating src/xalanc/Makefile
> config.status: creating src/xalanc/Utils/Makefile
> config.status: creating src/xalanc/Utils/MsgCreator/Makefile
> config.status: creating src/xalanc/Utils/XalanMsgLib/Makefile
> config.status: creating samples/Makefile
> config.status: creating Tests/Makefile
> 
> If the result of the above commands look OK to you, go to the 
> directory
> /user/sbhatnag/xalan/xml-xalan/c and type "gmake" or "make" 
> to make the 
> XALAN-C system.
> 
> Note: You must use GNU make to use the Xalan Makefile.
> 
> For each of these exe's, I get error like this:
> 
> gmake[3]: Entering directory 
> `/user/sbhatnag/xalan/xml-xalan/c/src/xalanc/Utils/MsgCreator'
> .....
> .....
> .....
> g++ -m64 -w -O3     -DXML_BITSTOBUILD_64  -D__sparc_v9__ 
> -ffor-scope 
> -fno-enforce-eh-specs -fno-const-strings -mcpu=ultrasparc3 
> -mtune=ultrasparc3  -fno-elide-constructors -Wall -fPIC -DSOLARIS 
> -D_REENTRANT -DXALAN_INMEM_MSG_LOADER -c 
> -I/user/sbhatnag/xalan/xml-xalan/c/src 
> -I/user/sbhatnag/xalan/xml-xalan/c/include -I../../../../nls/include 
> -I/user/sbhatnag/xerces/xerces-c-src_2_6_0/src/ 
> -I/user/sbhatnag/xerces/xerces-c-src_2_6_0/include/xercesc 
> -I/user/sbhatnag/xerces/xerces-c-src_2_6_0/include/  -o 
> ../../../../obj/SAX2Handler.o 
> /user/sbhatnag/xalan/xml-xalan/c/src/xalanc/Utils/MsgCreator/S
> AX2Handler.cpp
> g++ -DSOLARIS -fPIC -DXALAN_INMEM_MSG_LOADER   \
> -lc  -L/user/sbhatnag/xerces/xerces-c-src_2_6_0/lib -lxerces-c 
> ../../../../obj/MsgFileOutputStream.o ../../../../obj/ICUResHandler.o 
> ../../../../obj/InMemHandler.o ../../../../obj/MsgCreator.o 
> ../../../../obj/NLSHandler.o ../../../../obj/SAX2Handler.o -o 
> ../../../../bin/MsgCreator 
> ld: fatal: file 
> /user/sbhatnag/xerces/xerces-c-src_2_6_0/lib/libxerces-c.so: 
> wrong ELF 
> class: ELFCLASS64
> ld: fatal: file ../../../../obj/MsgFileOutputStream.o: wrong 
> ELF class: 
> ELFCLASS64
> ld: fatal: File processing errors. No output written to 
> ../../../../bin/MsgCreator
> collect2: ld returned 1 exit status
> gmake[3]: *** [../../../../bin/MsgCreator] Error 1
> gmake[3]: Leaving directory 
> `/user/sbhatnag/xalan/xml-xalan/c/src/xalanc/Utils/MsgCreator'
> 
> warm regards
> 
> Saurabh
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: c-dev-help@xerces.apache.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: c-dev-help@xerces.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org