Hello all,

I am wondering if it is possible to statically link to mcrypt libraries when compiling and linking my own c code? I get these errors when I do:

gcc -I/usr/local/include -c xx.c
gcc -o xx xx.o -L/usr/local/lib -lmcrypt -static

/usr/bin/ld: cannot find -lmcrypt
collect2: ld returned 1 exit status
make: *** [filtercmd] Error 1

I removed -lmcrypt and did this instead:

gcc -o xx xx.o -static /usr/local/lib/libmcrypt.so

This seems to link OK, but when I try to run the resultant
application, I get this:

/usr/lib/libc.so.1: bad ELF interpreter: No such file or directory

Yikes! Where is it trying to dynamically link this? But I'm not sure I even linked correctly anyway.

All this is on Fedora Core 2, BTW, with libmcrypt 2.5.7 installed from source (correctly, I think, since PHP uses it perfectly fine).

The code I am compiling is just VERY simple example code to get me going:

#include <mcrypt.h>
#include <stdlib.h>
int main(int argc, char *argv[]){
char *algo = "asdfasdf";
MCRYPT td;
td = mcrypt_module_open(algo, NULL, NULL, NULL);
}

= = = = = = = = = = = = = = = = = = = =

I also can't get it to link dynamically, which is NOT my first choice (due to other constraints):

When linking, I removed -static and the direct libmcrypt.so reference and added -lmcrypt -L/usr/local/lib:

gcc -o xx xx.o -L/usr/local/lib -lmcrypt

Which links OK, but this happens when running it:

error while loading shared libraries: libmcrypt.so.4: cannot open
shared object file: No such file or directory:

But I think this happens because I didn't compile mcrypt to use dynamic loading (see libmcrypt's README; it's not turned on by default). Again, static linking is my preference anyway.


mcrypt-devel list is ghostly quiet.... hoping there are actually ppl here.

TIA!!!!

I'm guessing /usr/local/lib isn't in your system default library search path. Either add /usr/local/lib to /etc/ld.so.conf and rerun ldconfig or simply add /usr/local/lib to your LD_LIBRARY_PATH environment variable.

Thank you for your help!

Unfortunately, although I did try adding /usr/local/lib to /etc/ld.so.conf, and that FIXES the problem when I link dynamically, I still cannot compile statically.

I am not clear about what environment LD_LIBRARY_PATH is in (and have NO IDEA if it will help when linking statically??). It's certainly not in a standard login shell. Is it something I should set when compiling? Linking? Any hints?

Thanks very much!

For the record:

echo "/usr/local/lib" >> /etc/ld.so.conf
ldconfig

THIS WORKS:

gcc -I/usr/local/include -c xx.c
gcc -o xx xx.o -L/usr/local/lib -lmcrypt
xx

THIS *DOES NOT* WORK:

gcc -I/usr/local/include -c xx.c

gcc -o xx xx.o -static -L/usr/local/lib -lmcrypt
/usr/bin/ld: cannot find -lmcrypt
collect2: ld returned 1 exit status

gcc -o xx xx.o -static -L/usr/local/lib
xx.o(.text+0x21): In function `main':
: undefined reference to `mcrypt_module_open'
collect2: ld returned 1 exit status

gcc -o xx xx.o -static /usr/local/lib/libmcrypt.so
# links OK, but same error when running the binary:
xx
bash: ./xx: /usr/lib/libc.so.1: bad ELF interpreter: No such file or directory

I'm having a similar problem, did you end up solving it?

Try:

My problem is with libc.a not libmcrypt.
I'm opening another thread for my problem.
http://www.linuxquestions.org/questi...hreadid=364076

Sorry, I didn't solve the problem. The libmcrypt list was not helpful, nor was this forum. You'd think there were other people actually using this software somewhere....?

freegianghu fails to note that the point is to link statically.

I eventually gave up and found another way around what I was trying to do.... and I don't remember what that was at the moment (sorry), but it was application specific anyway.

you probably got the wrong yum install.

try "yum install mcrypt-devel"