Hi All I did some more research on this and found that Xerces always is building 32 bit with GCC....is 64 bit not supported or am I making a mistake? I am attaching the runConfigure I am using.....
Step 1:
runConfigure -psolaris -cgcc -xg++ -b64 -z-mcpu=ultrasparc3
-l-mcpu=ultrasparc3 -P/tools/rd/gcc/xerces/c-2.6.0
(I got the same results with runConfigure -psolaris -cgcc -xg++ -b64 )
Step2:
gmake
Step3:
ELFDUMP for libxerces-c.so2.6
gmake[1]: Leaving directory `/user/sbhatnag/xerces/xerces-c-src_2_6_0/obj'
$ elfdump -e ../../lib/libxerces-c.so.26.0
ELF Header
ei_magic: { 0x7f, E, L, F }
ei_class: ELFCLASS32 ei_data: ELFDATA2MSB
e_machine: EM_SPARC32PLUS e_version: EV_CURRENT
e_type: ET_DYN
e_flags: [ EF_SPARC_32PLUS EF_SPARC_SUN_US1 EF_SPARC_SUN_US3 ]
e_entry: 0x94 e_ehsize: 52 e_shstrndx: 4859
e_shoff: 0x5af2d4 e_shentsize: 40 e_shnum: 4861
e_phoff: 0x34 e_phentsize: 32 e_phnum: 3
$
This matches with the 32 bit dump
ELF Header
ei_magic: { 0x7f, E, L, F }
ei_class: ELFCLASS32 ei_data: ELFDATA2MSB
e_machine: EM_SPARC32PLUS e_version: EV_CURRENT
e_type: ET_DYN
e_flags: [ EF_SPARC_32PLUS EF_SPARC_SUN_US1 EF_SPARC_SUN_US3 ]
e_entry: 0x94 e_ehsize: 52 e_shstrndx: 4859
e_shoff: 0x5af2d4 e_shentsize: 40 e_shnum: 4861
e_phoff: 0x34 e_phentsize: 32 e_phnum: 3
warm regards
Saurabh
Saurabh Bhatnagar/BLR/HTL
04/20/2005 05:08 PM
To
[email protected]
cc
Subject
Fw: Building Xerces 2.3.0 with GCC 3.4.2 on Solaris5.8!!!
Any takers for my query on the size of 64 vs 32 bit builds?
warm regards
Saurabh
----- Forwarded by Saurabh Bhatnagar/BLR/HTL on 04/20/2005 05:08 PM -----
Saurabh Bhatnagar/BLR/HTL
04/19/2005 04:03 PM
To
[email protected]
cc
[EMAIL PROTECTED], Akshya Pradhan/BLR/[EMAIL PROTECTED], Manikandan
Ganesan/BLR/[EMAIL PROTECTED]
Subject
Re: Building Xerces 2.3.0 with GCC 3.4.2 on Solaris5.8!!!
Hi Dave
Thanks for your inputs.
I am able to build Xalan from 18th Apr. CVS snapshot.
http://cvs.apache.org/snapshots/xml-xalan/xml-xalan_20050419042745.tar.gz
Is this 1.9 version?
Amazingly, I find that the 32 and 64 bit libraries are of the same size!!!
I built twice just to make sure, got the same result.
The only difference in the two. is that in 32 bit there are no symlinks
but in 64 it's as usual.
(We have built Xalan 1.7 where 64 bit libs were around 30% bigger than 32
bit ones. )
In my install directory
$ diff lib lib_64
$ ll lib
total 54888
-rwxrwxr-x 1 sbhatnag rd-tech 9310868 Apr 19 04:39 libxalan-c.so
-rwxrwxr-x 1 sbhatnag rd-tech 9310868 Apr 19 04:39 libxalan-c.so.19
-rwxrwxr-x 1 sbhatnag rd-tech 9310868 Apr 19 04:39 libxalan-c.so.19.0
-rwxrwxr-x 1 sbhatnag rd-tech 37884 Apr 19 04:39 libxalanMsg.so
-rwxrwxr-x 1 sbhatnag rd-tech 37884 Apr 19 04:39 libxalanMsg.so.19
-rwxrwxr-x 1 sbhatnag rd-tech 37884 Apr 19 04:39 libxalanMsg.so.19.0
$ ll lib_64
total 18296
lrwxrwxrwx 1 sbhatnag rd-tech 18 Apr 19 05:05 libxalan-c.so ->
libxalan-c.so.19.0
lrwxrwxrwx 1 sbhatnag rd-tech 18 Apr 19 05:05 libxalan-c.so.19 ->
libxalan-c.so.19.0
-rwxr-xr-x 1 sbhatnag rd-tech 9310868 Apr 19 05:05 libxalan-c.so.19.0
lrwxrwxrwx 1 sbhatnag rd-tech 19 Apr 19 05:05 libxalanMsg.so ->
libxalanMsg.so.19.0
lrwxrwxrwx 1 sbhatnag rd-tech 19 Apr 19 05:05 libxalanMsg.so.19 ->
libxalanMsg.so.19.0
-rwxr-xr-x 1 sbhatnag rd-tech 37884 Apr 19 05:05 libxalanMsg.so.19.0
$
Is this Okay?
warm regards
Saurabh
[EMAIL PROTECTED]
04/18/2005 10:39 PM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: Building Xerces 2.3.0 with GCC 3.4.2 on Solaris5.8!!!
> Hi Dave
>
> I was able to build Xerces 2.6.0 with GCC 3.4.2 but is it compatible
with
> Xalan 1.9?
That combination was never tested, so I don't know if it will be
compatible.
To build Xalan-C, regardless of the Xerces-C version, you'll need to use
the latest CVS. Also, please make sure you direct future Xalan-C
questions to the Xalan-C user list.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
runConfigure
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
