-
Notifications
You must be signed in to change notification settings - Fork 95
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
Compilation Issue #102
Comments
I also get the following error when trying to run the "make" command: Please let me know what I can do to resolve this! |
I have used the following command and it solved my problem. |
It worked well for me! thx! |
I get the following error message when compiling:
/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(timing.o): relocation R_X86_64_32 against
.text' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(aes.o): relocation R_X86_64_32 against
.bss' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(arc4.o): relocation R_X86_64_32 against
.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(base64.o): relocation R_X86_64_32S against
.rodata' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(blowfish.o): relocation R_X86_64_32S against
.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(camellia.o): relocation R_X86_64_32S against
.rodata' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(ccm.o): relocation R_X86_64_32 against
.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(chacha20.o): relocation R_X86_64_32 against
.rodata' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(chachapoly.o): relocation R_X86_64_32 against
.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(ecdsa.o): relocation R_X86_64_32S against symbol
mbedtls_hmac_drbg_random' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(hmac_drbg.o): relocation R_X86_64_32 against
.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(pkcs5.o): relocation R_X86_64_32 against
.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: /gpfs/share/apps/bam-readcount/1.0.1/bam-readcount/build/vendor/mbedtls/lib/libmbedcrypto.a(poly1305.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
make[5]: *** [libcurl.la] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [vendor/src/curl-stamp/curl-build] Error 2
make[1]: *** [CMakeFiles/curl.dir/all] Error 2
make: *** [all] Error 2
Adding -DCMAKE_CXX_FLAGS=-fPIC -DCMAKE_C_FLAGS=-fPIC to cmake didn't seem to help the issue.
I'd appreciate any help on this!
The text was updated successfully, but these errors were encountered: