Compile problem - configure: error: zm requires openssl/md5.

Support and queries relating to all previous versions of ZoneMinder
Locked
fbnts
Posts: 6
Joined: Mon Mar 21, 2005 10:37 pm

Compile problem - configure: error: zm requires openssl/md5.

Post by fbnts »

Sorry posted this in hardware by mistake!

Hi,

I'm tring to compile zm 1.22 but getting the below problem:

Code: Select all

configure: error: zm requires openssl/md5.h
I have check that openssl is installed but still cannnot get past this problem.


Any ideas?

Tom
mnmis
Posts: 21
Joined: Tue Oct 25, 2005 5:41 pm

Post by mnmis »

User avatar
zoneminder
Site Admin
Posts: 5215
Joined: Wed Jul 09, 2003 2:07 pm
Location: Bristol, UK
Contact:

Post by zoneminder »

I have done a patch on the configure.in file for 1.22.1. Unfortunately this is not a shipped file and is only used to generate the 'configure' script. In the meantime i would suggest doing as per the other thread and copying the md5.h section over from the 1.21.4 configure file. Essentially the problem occurs because another header file, stdlib.h, seems to have stopped being included by default and this contains a definition that configure needs when validating md5.h
Phil
fbnts
Posts: 6
Joined: Mon Mar 21, 2005 10:37 pm

Post by fbnts »

Thanks for the pointer - I have already tried that, but like one of the comments stated, the lines are identical.

I have reinstalled openssl and its got a symlink in /usr/include/md5.h to usr/include/openssl/md5.h

Any other ideas?

Tom
User avatar
zoneminder
Site Admin
Posts: 5215
Joined: Wed Jul 09, 2003 2:07 pm
Location: Bristol, UK
Contact:

Post by zoneminder »

Just to confirm you have the same problem, can you post the relevant section of your config.log file. It should have a small test program that includes md5.h, so just post from there on.
Phil
fbnts
Posts: 6
Joined: Mon Mar 21, 2005 10:37 pm

Post by fbnts »

hi thanks for the reply - didnt relise it created a log.

After looking in there it became clear that the it couldn't find openssl/md5.h

found out that the openssl directory only contained symlinks that were not valid. Repaired the directory and its configured fine!

Thanks for the pointer!

Tom
Locked