jeroen / openssl

OpenSSL bindings for R
Other
65 stars 23 forks source link

openssl installation failed on Suse Linux 11SP2 #23

Closed zqkal closed 8 years ago

zqkal commented 8 years ago

OS suse Linux 11SP2

I am trying to install the openssl package and running into issues. I have setup the Path variable as per the instructions but still getting the same error. Please advise.

Paths: k2uahp@algrid-ap01:~> echo $PKG_CONFIG_PATH /usr/lib64/pkgconfig/openssl.pc k2uahp@algrid-ap01:~> echo $PATH|grep pkg-config /usr/bin/pkg-config:/usr/fnma/bin:/bin:/usr/bin:/usr/SYSADM/bin:/appl/tools/R2/bin:/appl/tools/R2/bin:/appl/tools/R2/bin k2uahp@algrid-ap01:~>

Error:

2016-04-25 17:37:49 (2.63 MB/s) - `/tmp/Rtmpy3rxM0/downloaded_packages/openssl_0.9.2.tar.gz' saved [882041/882041]

The downloaded source packages are in ‘/tmp/Rtmpy3rxM0/downloaded_packages’ Warning message: In install.packages("openssl") : installation of package ‘openssl’ had non-zero exit status


openssl version -a OpenSSL 0.9.8j-fips 07 Jan 2009 built on: Wed Jun 4 12:08:22 UTC 2014 platform: linux-x86_64 options: bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,4,long) blowfish(ptr2) compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DMD32_REG_T=int -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fomit-frame-pointer -fno-strict-aliasing -DTERMIO -Wall -fstack-protector -Wa,--noexecstack -fprofile-use -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM OPENSSLDIR: "/etc/ssl"

jeroen commented 8 years ago

You need openssl 1.0 or greater. See also the system requirements on the cran page. The version of openssl you are running (0.9.8j) is almost 7 years old. I hope your vendor can you provide with newer versions some way or another. Otherwise you might need to build libssl from source.

In addition: usually you shouldn't have to set PKG_CONFIG_PATH if you use the system pkg-config. But if you do set it, it must be a path (not the pc file) e.g.: PKG_CONFIG_PATH=/usr/lib64/pkgconfig

zqkal commented 8 years ago

Thank you so much for the prompt response.

Kalkidan Lebeta Thanks

On Apr 26, 2016, at 11:41 AM, Jeroen Ooms notifications@github.com wrote:

You need openssl 1.0 or greater. See also the system requirements on the cran page.

In addition: usually you shouldn't have to set PKG_CONFIG_PATH if you use the system pkg-config. But if you do set it, it must be a path (not the pc file) e.g.: PKG_CONFIG_PATH=/usr/lib64/pkgconfig

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub