Re: is it me or ...
Jason wrote: >does openssl-0.9.7i not respect LDFLAGS?? >Im trying to set the rpath and cannot get it set for some reason.. > >[EMAIL PROTECTED] ldd /local/stuff/bin/openssl >libssl.so.0.9.7 => (file not found) >libcrypto.so.0.9.7 =>(file not found) >libsocket.so.1 =>/usr/lib/libsocket.so.1 >libnsl.so.1 => /usr/lib/libnsl.so.1 >libdl.so.1 =>/usr/lib/libdl.so.1 >libc.so.1 => /usr/lib/libc.so.1 >libmp.so.2 =>/usr/lib/libmp.so.2 >/usr/platform/SUNW,UltraAX-e2/lib/libc_psr.so.1 >[EMAIL PROTECTED] > >and of course libcrypto.so.0.9.7 and libssl.so.0.9.7 are in /local/stuff/lib >and im trying to use >LDFLAGS='-L/local/stuff/lib -R/local/stuff/lib';export LDFLAGS >in my configure script, but openssl wont use it >this is gcc 3.4.2 on solaris 8. > >Jason > > Use LD_OPTIONS instead of LDFLAGS if you use the ld provided by Sun. You can then do a dump -Lv on your object to see if RPATH is indeed set. /A __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: Having problem compillin in solaris 10.
Hi, First; are you using the right PATH to the compilers? as in /opt/SUNWspro/bin or /usr/sfw/bin before any other path to other locations of gcc? for Sun CC I suggest; export PATH=/usr/bin:/opt/SUNWspro/bin:/usr/ccs/bin gcc: export PATH=/usr/bin:/usr/sfw/bin:/usr/ccs/bin Next, when using Sun CC you must supply -xarch=amd64 for producing 64-bit amd64 version1 binaries. Also, make sure your linker is aware of the 64-bit paths; -R/usr/lib/64 -L/usr/lib/64 or -R/usr/sfw/lib/amd64 -L/usr/sfw/lib/amd64 alternatively, use $ISALIST for automatic detection at run-time. I usually use the LD_OPTIONS environment variable when building for CSW, so first do; export LD_OPTIONS='-R/usr/lib/$ISALIST -L/usr/lib/amd64' or with sfw... /usr/sfw/bin/gcc compiles amd64 just fine, so I'm fairly convinced it is your paths that point to the gcc that can't do 64-bit. /Andreas Lisandro Grullon wrote: Hi Andrea, I installed the Sun C compiler suite as you pointed out; however, after defining the path as suggested by the Sun C compiler instructions things still not working properly and I still getting the same compilation error. I also checked in /usr/sfw/bin for my gcc compiler and I see that it is there; however, it doesn't seem to be compiling via the -m64 option. This is so weird, whoever design these compilers should make the stuff work automatically if I am working in either 32 or 64 bit architecture. Ohhh well, this is the error (same) as my previous. Any other sugestions to get this going? bash-3.00# make making all in crypto... ( echo "#ifndef MK1MF_BUILD"; \ echo ' /* auto-generated by crypto/Makefile for crypto/cversion.c */'; \ echo ' #define CFLAGS "gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM"'; \ echo ' #define PLATFORM "solaris64-x86_64-gcc"'; \ echo " #define DATE \"`LC_ALL=C LC_TIME=C date`\""; \ echo '#endif' ) >buildinf.h gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c cryptlib.c cc1: sorry, unimplemented: 64-bit mode not compiled in *** Error code 1 make: Fatal error: Command failed for target `cryptlib.o' Current working directory /download/openssl-0.9.8/crypto *** Error code 1 The following command caused the error: dir=crypto; target=all; if [ -d "$dir" ]; then ( cd $dir && echo "making $target in $dir..." && TOP= && unset TOP ${LIB+LIB} ${LIBS+LIBS}${INCLUDE+INCLUDE} ${INCLUDES+INCLUDES} ${DIR+DIR} ${DIRS+DIRS} ${SRC+SRC} ${LIBSRC+LIBSRC} ${LIBOBJ+LIBOBJ} ${ALL+ALL}${EXHEADER+EXHEADER} ${HEADER+HEADER} ${GENERAL+GENERAL} ${CFLAGS+CFLAGS} ${ASFLAGS+ASFLAGS} ${AFLAGS+AFLAGS} ${LDCMD+LDCMD} ${LDFLAGS+LDFLAGS} ${SHAREDCMD+SHAREDCMD} ${SHAREDFLAGS+SHAREDFLAGS} ${SHARED_LIB+SHARED_LIB} ${LIBEXTRAS+LIBEXTRAS} && make -e PLATFORM='solaris64-x86_64-gcc' PROCESSOR='' CC='gcc' CFLAG='-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM'AS='gcc' ASFLAG='-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c' AR='ar r' PERL='/usr/bin/perl' RANLIB='/usr/ccs/bin/ranlib'SDIRS='objects md2 md4 md5 sha hmac ripemd des aes rc2 rc4 idea bf cast bn ec rsa dsa ecdsa dh ecdh dso engine buffer bio stack lhash rand err evp asn1 pem x509 x509v3 conf txt_db pkcs7 pkcs12 comp ocsp ui krb5 store pqueue' LIBRPATH='/usr/local/ssl/lib'INSTALL_PREFIX='' INSTALLTOP='/usr/local/ssl' OPENSSLDIR='/usr/local/ssl' MAKEDEPEND='$${TOP}/util/domd $${TOP} -MD gcc' DEPFLAG='-DOPENSSL_NO_DEPRECATED -DOPENSSL_NO_GMP -DOPENSSL_NO_MDC2 -DOPENSSL_NO_RC5' MAKEDEPPROG='gcc' SHARED_LDFLAGS='-m64 -shared -static-libgcc'KRB5_INCLUDES='' LIBKRB5='' EXE_EXT='' SHARED_LIBS='' SHLIB_EXT='.so.0.9.8' SHLIB_TARGET='solaris-shared' PEX_LIBS='' EX_LIBS='-lsocket -lnsl -ldl' CPUID_OBJ='x86_64cpuid.o' BN_ASM='x86_64-gcc.o' DES_ENC='des_enc.o fcrypt_b.o'AES_ASM_OBJ='aes_core.o aes_cbc.o' BF_ENC='bf_enc.o' CAST_ENC='c_enc.o'RC4_ENC='rc4-x86_64.o' RC5_ENC='rc5_enc.o' SHA1_ASM_OBJ='' MD5_ASM_OBJ='md5-x86_64.o' RMD160_ASM_OBJ='' THIS=${THIS:-build_crypto} MAKEFILE=Makefile MAKEOVERRIDES= TOP=.. DIR=$dir $target ) || exit 1; fi make: Fatal error: Command failed for target `build_crypto' Thanks Andrea and Sean for replying. --- Lisandro Grullon New York City College of Technology Division of Continuing Education Director of Network Operations Lisandro Office:1718-552-1178 Lisandro E-mail:
Re: Having problem compillin in solaris 10.
Hi, For the Sun C compiler suite; http://www.opensolaris.org/os/community/tools/sun_studio_tools/ (Check license terms though) The GCC for amd64 may be installed on your system in /usr/sfw, in the case you have installed Companion CD I believe. Else, you will have to install it from CD, or compile GCC yourself with the "-target x86_64" specified. I'm not sure about other distributions... Good luck, Andreas Lisandro Grullon wrote: >Andrea, can you point me in the right direction where to find the compiler to >supportamd64. thanks. > >--- >Lisandro Grullon >New York City College of Technology >Division of Continuing Education >Director of Network Operations >Lisandro Office:1718-552-1178 >Lisandro E-mail: [EMAIL PROTECTED] >"Unix is user-friendly. It's just very selective about who its friends are." > > > [EMAIL PROTECTED] 09/01/05 2:48 AM >>> >Lisandro Grullon wrote: > > > >>Hi there, >> >>I am having some issues compiling openssl 0.9.8. Bellow I am pasting the >>output of the errors. I apreciate your help. I am running Solaris 10 x86 >>opteron. >> >> >> >> >> > > > > >>echo '#endif' ) >buildinf.h >>gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN >>-DHAVE_DLFCN_H -m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c >>cryptlib.c >>cc1: sorry, unimplemented: 64-bit mode not compiled in >>*** Error code 1 >>make: Fatal error: Command failed for target `cryptlib.o' >>Current working directory /export/download/openssl-0.9.8/crypto >>*** Error code 1 >> >> >> >> >Well, the message is clear, gcc does not support the 64-bit target in >this case. You could try to compile it with Sun's C compiler, it has >full support for amd64 target, or alternatively you find a gcc >distribution that has support for amd64 compiled in. >The Sun C compiler is free for use in open-source projects, such as >opensolaris, so you might be eligble for free download. > >/Andreas > > > >__ >OpenSSL Project http://www.openssl.org >User Support Mailing Listopenssl-users@openssl.org >Automated List Manager [EMAIL PROTECTED] > >__ >OpenSSL Project http://www.openssl.org >User Support Mailing Listopenssl-users@openssl.org >Automated List Manager [EMAIL PROTECTED] > > > > > -- == http://www.almroth.com| Phone/Fax: +44 (0)700 397 3283 http://www.blastwave.org - maintainer | [EMAIL PROTECTED] == signature.asc Description: OpenPGP digital signature
Re: Having problem compillin in solaris 10.
Lisandro Grullon wrote: Hi there, I am having some issues compiling openssl 0.9.8. Bellow I am pasting the output of the errors. I apreciate your help. I am running Solaris 10 x86 opteron. echo '#endif' ) >buildinf.h gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c cryptlib.c cc1: sorry, unimplemented: 64-bit mode not compiled in *** Error code 1 make: Fatal error: Command failed for target `cryptlib.o' Current working directory /export/download/openssl-0.9.8/crypto *** Error code 1 Well, the message is clear, gcc does not support the 64-bit target in this case. You could try to compile it with Sun's C compiler, it has full support for amd64 target, or alternatively you find a gcc distribution that has support for amd64 compiled in. The Sun C compiler is free for use in open-source projects, such as opensolaris, so you might be eligble for free download. /Andreas __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: Runpath definition missing for libssl.so
Laurent Blume wrote: prakash babu wrote: *Solution 1 :* Create a symbolic link in the system directory for libcrypto.so and libssl.so ln -s /usr/local/openssl-0.9.7g/lib/libcrypto.so /usr/lib/libcrypto.so ln -s /usr/local/openssl-0.9.7g/lib/libssl.so /usr/lib/libssl.so Evil. This is a sure road to troubles at some point (I know, some dumb sysadmins have messed with a few boxes in such ways before I arrived, they're a real PITA to update now). *Solution 2* Specify a embedded path for the library using the flag* -Wl,+b /usr/local/openssl-0.9.7g/lib* (not sure for SunCC) Yes, but how do I pass it along using the config script? -R should have done it. Thanks for answering! As it is Solaris, use export LD_OPTIONS='-R/usr/local/openssl-0.9.7g/lib -L/usr/local/openssl-0.9.7g/lib' The linker will take that into consideration, and if you do a dump -Lv on the output file, the RUNPATH should be included. /Andreas __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]