-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue in building dependencies #2
Comments
Hi @gitrohit, What architecture are you trying to build OpenSSL for? From your log output it seems that you have selected 32bit. Is your system 64bit? In that case maybe you are missing some libraries to be able to generate 32bit binaries. Try running the following command to see if it solves the issue:
I tested the compilation in a 64bit CentOS 7.6 Docker container after installing those packages and it worked. I also found this stackoverflow answer that states that "static linking is explicity unsupported on Red Hat Enterprise Linux", which is your current OS. BlackICE Connect is designed to be statically linked, so you'll need to check if the before statement is true or not. In case you are not able to build BlackICE Connet statically you could try one of the available releases. Also I found an error in the configuration of the dependency zlib for the 32 bit case and I've just corrected it. In case you've already built it, please do it again because the configure step was pointing the install directory of zlib to the 64 bit path. Please let me know if you were able to solve the issue. Thank you. |
Hi, Yes my machine is 64 bit. I got same error even after running yum install command you shared. It didn't help. I didn't get what you meant by following statement "...In case you are not able to build BlackICEConncet statically you could try one of the available releases." I got error while building Linux Dependencies as per the steps mentioned I have not yet started compiling BlackICEConnect package. I downloaded the BlackICEConnect package from same location which you shared. Does the package downloaded from this location not required to be build? Your statement Thanks |
You only need to build it if you download the source code package, but if you don't want (or can't) build it you can download one of the precompiled versions GradiantBlackIceConnect_PKCS11_linux_x64.tar.gz or GradiantBlackIceConnect_PKCS11_linux_x86.tar.gz |
I downloaded GradiantBlackIceConnect_PKCS11_linux_x86.tar.gz from https://github.com/Gradiant/BlackICE_Connect/releases. Is it tested/work on RHEL ? |
No, it is not tested on RHEL. The Linux version was built and tested only on Ubuntu, but it might work on other Linux distributions. I don't have a RHEL machine to test it on. If it works on your RHEL I would appreciate if you told me. |
Sure. Let me test |
After resolving mono issue mentioned above, not sure why it throws following error when running test script. Since I'm running it in RHEL, it shouldn't ask for .exe file. Cannot open assembly '/root/software/nunit-3.9/tools/NUnit.ConsoleRunner/tools/nunit3-console.exe': No such file or directory. Is the test script supposed to run on Windows? |
Hi, The tests for the PKCS#11 library are written in C# and run with the framework NUnit. In order to compile them in linux mono-devel package and the nunit framework are needed. The script
This binary is a .NET binary and is used to run the tests. It can be run in Linux using mono. From the error you are getting:
I suppose this is happening because you don't have the NUnit framework in that path. As stated here you can install the needed NUnit framework with the following commands:
Also from your second screenshot I guess you have installed mono manually. If you want you can install it from the Mono RHEL repo following these instructions. The PCKS#11 library tests are designed to be run only against the 64bit library. From your previous posts I assume you are using the 32bit version. So if you want to run the tests you can follow these steps: Download the 64 bit version of the PKCS#11 library. Uncompress and install it: Follow the steps of the installation procedure. After the installation is finished run the following commands: Edit the following line of the file To point to the directory where the file After these steps go to the directory
Please let me know if you are able to run the tests or if some of these steps are not clear. |
Hi, As for mono, I did it manually and was able to resolve mono related error posted earlier. My machine is 64 bit and I'm using 'GradiantBlackIceConnect_PKCS11_linux_x86.tar.gz'. Is that 32 bit version as mentioned by you? |
Yes, GradiantBlackIceConnect_PKCS11_linux_x86.tar.gz is the 32 bit version and GradiantBlackIceConnect_PKCS11_linux_x64.tar.gz is the 64 bit version. |
After downloading nunit and running buil script it throws error Does it needs mono 4.5 only as my installed version is 4.6.2.? |
Could you try the mono version from here instead the manual installed one to see if it resolves the issue? |
Build script of NUnit gives following error. Modified build file to echo nuget.exe path. Not sure why it's throwing ' Could not restore NuGet tools' error. Error: As for mono installation I can't do yum install because I'm behind firewall. I did manual installation of 4.6.2. |
Hi,
I'm trying to build dependencies before compiling the BlackIceConnect Connector but OpenSSL build is failing with error.
Environment:
RHEL 7.6
Error:
make[2]: Entering directory
/home/bcadmin/blackiceconnect/openssl-1.0.2n/apps' make[2]: warning: jobserver unavailable: using -j1. Add
+' to parent make rule.( :; LIBDEPS="${LIBDEPS:--L.. -lssl -L.. -lcrypto -ldl -L/home/bcadmin/blackiceconnect/zlib-1.2.11/libs/linux/zlib/release/x86/lib -lz}"; LDCMD="${LDCMD:-gcc -m32}"; LDFLAGS="${LDFLAGS:--DZLIB -DDSO_DLFCN -DHAVE_DLFCN_H -m32 -fPIC -static -Wa,--noexecstack -DL_ENDIAN -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM}"; LIBPATH=
for x in $LIBDEPS; do echo $x; done | sed -e 's/^ *-L//;t' -e d | uniq
; LIBPATH=echo $LIBPATH | sed -e 's/ /:/g'
; LD_LIBRARY_PATH=$LIBPATH:$LD_LIBRARY_PATH ${LDCMD} ${LDFLAGS} -o ${APPNAME:=openssl} openssl.o verify.o asn1pars.o req.o dgst.o dh.o dhparam.o enc.o passwd.o gendh.o errstr.o ca.o pkcs7.o crl2p7.o crl.o rsa.o rsautl.o dsa.o dsaparam.o ec.o ecparam.o x509.o genrsa.o gendsa.o genpkey.o s_server.o s_client.o speed.o s_time.o apps.o s_cb.o s_socket.o app_rand.o version.o sess_id.o ciphers.o nseq.o pkcs12.o pkcs8.o pkey.o pkeyparam.o pkeyutl.o spkac.o smime.o cms.o rand.o engine.o ocsp.o prime.o ts.o srp.o ${LIBDEPS} )/bin/ld: cannot find -ldl
/bin/ld: cannot find -lc
collect2: error: ld returned 1 exit status
make[2]: *** [link_app.] Error 1
make[2]: Leaving directory
/home/bcadmin/blackiceconnect/openssl-1.0.2n/apps' make[1]: *** [openssl] Error 2 make[1]: Leaving directory
/home/bcadmin/blackiceconnect/openssl-1.0.2n/apps'make: *** [build_apps] Error 1
[bcadmin@bc-05-phx openssl-1.0.2n]$ cd apps/
[bcadmin@bc-05-phx apps]$ ll
The text was updated successfully, but these errors were encountered: