Re: [Mcrypt-developers] linking statically and/or error while loading shared libraries

[Tod T. <tt...@ch...>]

email builder wrote:
> --- email builder <ema...@ya...> wrote:
> 
>>Update (but still looking for help!):
>>
>>
>>>=======
>>>
>>> 1) I am wondering if it is possible to statically link to mcrypt
>>
>>libraries
>>
>>>when compiling and linking my own 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 guess I am showing what a newbie I am.  I think I have to remove -lmcrypt
>>and do this instead:
>>
>>gcc -o xx xx.o -L/usr/local/lib -static /usr/local/lib/libmcrypt.so
> 
> 
> 
> Sorry, that's actually supposed to be
> 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!  I will go back to Google, but I have no idea what this means... why
>>is libc.so now creating problems?  What does that have to do with
>>libmcrypt?
>>
>>All this is on Fedora Core 2, BTW.

Try running ldd against the compiled executable and post the results.