Am Donnerstag, 14. Juni 2007 14:20 schrieb Ken Moffat:
> On Thu, Jun 14, 2007 at 12:02:25PM +0200, Gerhard Erker wrote:
> > Hello,
> > I'm a newbie on blfs and have a problem. I built a clfs-system with
> > only 64-bit. It workes fine.
> > I tried to build w3m. I installed GC-6.8 and pkg-config-0.20. Also I
> > installed openssl-0.9.8d. When compiling w3m I got the following error:
> >
> > in file included from fm.h:39,
> >                          from main.c:3:
> > html.h:5:25: Error: openssl/bio.h file or directory not found
> > html.h:6:26: Error: openssl/x509.h file or directory not found
> > html.h:7:25: Error: openssl/ssl.h file or directory not found
>
>  So, the openssl headers are not where w3m expects.  I'm on an LFS
> box at the moment, and for me openssl-0.9.8d put the headers into
> /usr/include/openssl.  On pure64 (x86_64) I build it with similar
> instructions to what is in development blfs for 0.9.8e. (Hmm, so I
> missed the newer version.)
>
>  Looks as if something went wrong with your openssl install, but I
> don't know what.  I see that cblfs has a patch to openssl for
> gcc-4.2.0, if you are using a recent clfs development book - not
> necessary for gcc-4.1.x.
>
> ĸen
> --
> das eine Mal als Tragödie, das andere Mal als Farce

Hello,
Many thanks for your help. When I read your answer, I looked into my clfs-box 
and saw, that there are no headers installed. So I searched and found the 
file './Configure' and the file './configure'. Unfortunately the scripts are 
not GNU so I had to look into both scripts. In the script ./Configure I 
found 'linux-x86_64'.
Then I started compiling with the 
following: ./Configure --openssldir=/etc/ssl --prefix=/usr shared 
linux-x86_64
and all worked fine. Once again many thanks. I think it would be good for 
other people if a hint would be in the wiki to openssl - but it could also be 
that this problem is only my problem.

With kind regards

Gerhard Erker
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to