RE: Error: relocations based on the ABS44 coding model can not be used in building a shared object
HI my problem is solved by using option shared with ./Configure. Thanks for your consistent support and quick response. From: BISHT, SEEMANT (SEEMANT) Sent: 19 August 2010 20:15 To: Tim Hudson; t...@cryptsoft.com Cc: 'openssl-users@openssl.org' Subject: RE: Error: relocations based on the ABS44 coding model can not be used in building a shared object Hi Time, Iam still facing the same issue. Actually I need to have .so similar to libssl.so libcrypto.so but just single one. And also I need to have the same in 64 Bit. Iam still getting the same error: ld: fatal: relocation error: R_SPARC_H44: file ssl/s2_meth.o: symbolunknown: relocations based on the ABS44 coding model can not be used in building a shared object One more theing to mention while doing ldd s2_math.o Iam having the following error: GNM056 linus cd ssl GNM056 linus pwd /osp/sde/Icc50_mnt_V01_view/lib/velizy/standard/openssl2/openssl2-0.9.8o/ssl GNM056 linus ldd s2_meth.o warning: ldd: s2_meth.o: is not executable ld.so.1: /usr/lib/sparcv9/lddstub: fatal: relocation error: R_SPARC_H44: file ./s2_meth.o: symbol unknown: relocations based on the ABS44 coding model can not be used in building a shared object ldd: s2_meth.o: execution failed due to signal 11 (core dumped) GNM056 linus That's why I think there is some problem in compilation of openssl because of which Iam having this error in ldd. Please help me out. Thanks. From: Tim Hudson [mailto:tim.hud...@pobox.com] Sent: 19 August 2010 09:43 To: BISHT, SEEMANT (SEEMANT) Subject: Re: Error: relocations based on the ABS44 coding model can not be used in building a shared object On 19/08/2010 2:01 AM, BISHT, SEEMANT (SEEMANT) wrote: Hi Tim, Thank you very much. I moved forward using your suggestion. But again Iam stuck at one point. (1) Iam facing problem in creating my specific .so. Iam having error: ld: fatal: relocation error: R_SPARC_H44: file ssl/s2_meth.o: symbolunknown: relocations based on the ABS44 coding model can not be used in building a shared object Iam using makefile: INCSO += -lsocket -lnsl -ldl -lkstat -lsunmath -lm CFLAGS = -xO4 -xarch=v9 -xcode=abs64 -G export CFLAGS Remove the -xcode=abs64 (actually I'd remove most of your CFLAGS definition - you should not need it - except perhaps the -G) You are now dealing with build issues in your code and not openssl. ar t libssl.a shows the list of objects in libssl.a ar t libcrypto.a will show the objects in libcrypto.a which libssl.a needs I haven't built an openssl solaris shared library configuration in a while - so I'd have to power on some of my solaris machines to check 0 however I don't think it is anything to do with openssl. BTW I didn't get the direct email to t...@cryptsoft.commailto:t...@cryptsoft.com so I've switched to an address which you might find easier to reach. Tim
RE: Error: relocations based on the ABS44 coding model can not be used in building a shared object
Hi Time, Iam still facing the same issue. Actually I need to have .so similar to libssl.so libcrypto.so but just single one. And also I need to have the same in 64 Bit. Iam still getting the same error: ld: fatal: relocation error: R_SPARC_H44: file ssl/s2_meth.o: symbolunknown: relocations based on the ABS44 coding model can not be used in building a shared object One more theing to mention while doing ldd s2_math.o Iam having the following error: GNM056 linus cd ssl GNM056 linus pwd /osp/sde/Icc50_mnt_V01_view/lib/velizy/standard/openssl2/openssl2-0.9.8o/ssl GNM056 linus ldd s2_meth.o warning: ldd: s2_meth.o: is not executable ld.so.1: /usr/lib/sparcv9/lddstub: fatal: relocation error: R_SPARC_H44: file ./s2_meth.o: symbol unknown: relocations based on the ABS44 coding model can not be used in building a shared object ldd: s2_meth.o: execution failed due to signal 11 (core dumped) GNM056 linus That's why I think there is some problem in compilation of openssl because of which Iam having this error in ldd. Please help me out. Thanks. From: Tim Hudson [mailto:tim.hud...@pobox.com] Sent: 19 August 2010 09:43 To: BISHT, SEEMANT (SEEMANT) Subject: Re: Error: relocations based on the ABS44 coding model can not be used in building a shared object On 19/08/2010 2:01 AM, BISHT, SEEMANT (SEEMANT) wrote: Hi Tim, Thank you very much. I moved forward using your suggestion. But again Iam stuck at one point. (1) Iam facing problem in creating my specific .so. Iam having error: ld: fatal: relocation error: R_SPARC_H44: file ssl/s2_meth.o: symbolunknown: relocations based on the ABS44 coding model can not be used in building a shared object Iam using makefile: INCSO += -lsocket -lnsl -ldl -lkstat -lsunmath -lm CFLAGS = -xO4 -xarch=v9 -xcode=abs64 -G export CFLAGS Remove the -xcode=abs64 (actually I'd remove most of your CFLAGS definition - you should not need it - except perhaps the -G) You are now dealing with build issues in your code and not openssl. ar t libssl.a shows the list of objects in libssl.a ar t libcrypto.a will show the objects in libcrypto.a which libssl.a needs I haven't built an openssl solaris shared library configuration in a while - so I'd have to power on some of my solaris machines to check 0 however I don't think it is anything to do with openssl. BTW I didn't get the direct email to t...@cryptsoft.commailto:t...@cryptsoft.com so I've switched to an address which you might find easier to reach. Tim
Error: relocations based on the ABS44 coding model can not be used in building a shared object
Hi Tim, Thank you very much. I moved forward using your suggestion. But again Iam stuck at one point. (1) Iam facing problem in creating my specific .so. Iam having error: ld: fatal: relocation error: R_SPARC_H44: file ssl/s2_meth.o: symbolunknown: relocations based on the ABS44 coding model can not be used in building a shared object Iam using makefile: INCSO += -lsocket -lnsl -ldl -lkstat -lsunmath -lm CFLAGS = -xO4 -xarch=v9 -xcode=abs64 -G export CFLAGS LIB_SO = myown.so LIB_OBJS= ssl/s2_meth.o CC -xO4 -xarch=v9 -xcode=abs64 -KPIC -G -o $(LIB_SO) -DS_SUN -Qoption ld '-t' $(LIB_OBJS) $(INCSO) -lc Please show me the right direction to solve the issue. (2) Also please list me the .o file that need to be included in $(LIB_OBJS) to create .so that includes all the .o files included in libssl.so libcrypto.so. Actually I have to create my own specific .so that includes all the libraries included in libssl.so libcrypto.so. Thanks for your support. Waiting for response. Thanks Regards, Seemant Bisht. Alcatel Ph. No. +91-124-4133453 Mobile: +919810063317 Alcatel-Lucent India Building No.1, Fourth Floor, Seat No.59 Plot No.406, Udyog Vihar, Phase III Gurgaon 122016 P Think of the environmental impact before printing From: Tim Hudson [mailto:t...@cryptsoft.com] Sent: 18 August 2010 02:37 To: openssl-users@openssl.org Cc: BISHT, SEEMANT (SEEMANT) Subject: Re: wrong ELF class: ELFCLASS32 On 17/08/2010 7:03 PM, BISHT, SEEMANT (SEEMANT) wrote: Can you please tell me how to compile openssl library in 64-bit type? As when compiling the openssl, and checking If it was a linux intel based setup if would be: ./Configure linux-x86_64 or ./Configure linux-generic64 However given you seem to be on a sparc box: ./Configure solaris64-sparcv9-gcc or ./Configure solaris64-sparcv9-cc (depending on if you are using GCC or the Sun compiler) Look at the various targets available in the Configure script for more information. Then the usual make clean all Tim.
wrong ELF class: ELFCLASS32
Can you please tell me how to compile openssl library in 64-bit type? As when compiling the openssl, and checking GNM056 sdefile bio_ssl.o bio_ssl.o: ELF 32-bit MSB relocatable SPARC32PLUS Version 1, V8+ Required GNM056 sde I need it to be in 64 bit as I need to link this library with my existing .so that is in 64 bit. My .so: GNM056 sdefile libsib_velizy_generic_uns_HTTPSClient.so libsib_velizy_generic_uns_HTTPSClient.so: ELF 64-bit MSB dynamic lib SPARCV9 Version 1, dynamically linked, not stripped GNM056 sde As compiling my .so with openssl .so. I am having error: ld: fatal: file /openssl-0.9.8o/ssl/bio_ssl.: wrong ELF class: ELFCLASS32 Please show me the way. Thanks. Thanks Regards, Seemant Bisht. Alcatel Ph. No. +91-124-4133453 Mobile: +919810063317 Alcatel-Lucent India Building No.1, Fourth Floor, Seat No.59 Plot No.406, Udyog Vihar, Phase III Gurgaon 122016 P Think of the environmental impact before printing
