>       From: owner-openssl-us...@openssl.org On Behalf Of starfish Trousers
>       Sent: Thursday, 16 April, 2009 02:35

>       I googled and found some familiar solutions about my problem 
> and the solution is to make symbolic link due to the missing link:
        
>       copy it from lib/libssl to lib/libssl/include
        
>       however I could not find my libssl in any of my directory. can
somebody help me on this? 

That looks like it was intended to be an install location, for some 
sort of defective installation or packaging. I doubt it applies to you.

> I have also tried to edit my Makefile by changing:
>       
>       LIBCRYPTO=-L.. -lcrypto
>       LIBSSL=-L.. -lssl
>       to 
>       LIBCRYPTO=../libcrypto.a
>       LIBSSL=../libssl.a
>       
>       but it still fails. please, anyone? thanks in advance.

-L and -l (ell) only affect linking but you have a compilation problem.
You appear not to understand the basics of C programming.
        
>       From: starfish Trousers <lucyantie_trous...@yahoo.com>
>       To: openssl-users@openssl.org

>       I'm trying to compile /apps/ca.c from the openssl in the process 
> to create a single binary for revocation. I have initially face 
> this problem whereby I received below error: 

I don't understand 'a single binary for revocation', or why the ca.o 
and (monolith) openssl built by the normal build procedure aren't OK 
for you, but that isn't important.
        
>       In file included from ca.c:91:
>       apps.h:115:18: error: e_os.h: No such file or directory
<snip rest>
>       Can anyone tell me what is actually missing and how do 
> i suppose to fix it? thank you in advance.

What's missing is some(?) of the option(s) to tell the compiler 
where to find include files. For most compilers these are -I (eye) options 
set by the Makefile, and with the distro apps/Makefile I have on Linux 
it works. (Note it does not automatically grab dependencies and options
from the top=../Makefile, as it does for the monolith, so you need to 
make sure any changed compile settings you put in the top Makefile are 
(manually) copied, and ../lib{crypto,ssl}.a are up to date.)

If you're using a make, what exactly compile command line did it 
generate (and display)? If you're generating (or entering?) the 
compile command by other means, what exactly is it?



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to