Bug #2331: Undefined symbols _MD5_Update _MD5_Init _MD5_Final - Lighttpd - lighty labs

Actions

Copy link

Bug #2331

closed

Undefined symbols _MD5_Update _MD5_Init _MD5_Final

Added by ryandesign over 13 years ago. Updated over 13 years ago.

Status:

Fixed

Priority:

Normal

Category:

build_autotools

Target version:

1.4.30

ASK QUESTIONS IN Forums:

Description

I am the maintainer of lighttpd in MacPorts and I noticed when trying to update the port to version 1.4.29 that it does not build on Mac OS X 10.6.8 with Xcode 3.2.6:

Undefined symbols:
  "_MD5_Update", referenced from:
      _mod_usertrack_uri_handler in mod_usertrack.o
      _mod_usertrack_uri_handler in mod_usertrack.o
      _mod_usertrack_uri_handler in mod_usertrack.o
      _mod_usertrack_uri_handler in mod_usertrack.o
      _mod_usertrack_uri_handler in mod_usertrack.o
  "_MD5_Init", referenced from:
      _mod_usertrack_uri_handler in mod_usertrack.o
  "_MD5_Final", referenced from:
      _mod_usertrack_uri_handler in mod_usertrack.o
ld: symbol(s) not found
collect2: ld returned 1 exit status

lighttpd 1.4.28 built fine on this system.

Files

main.log (150 KB) main.log

ryandesign, 2011-07-27 02:28

Actions

Copy link

Updated by stbuehler over 13 years ago

Target version set to 1.4.30

Actions

Copy link

Updated by stbuehler over 13 years ago

Hm right. Broken by r2788 and r2790; it works on systems that don't care about unresolved symbols at compile time (like linux), as lighttpd is linked against ssl which will make the needed symbols available before loading the modules.

There are two options: link modules that need md5 against ssl (if enabled), or always use the md5 algorithm we include in lighttpd.

Actions

Copy link

Updated by ryandesign over 13 years ago

I should add that this problem only happens if I configure lighttpd with --with-openssl. If I don't do that, it builds fine. But, we do enable ssl by default in MacPorts, and I think that's a good default.

Actions

Copy link