I suspect they're really the same routines (public domain
impl of MD5), but it's reasonable to expect that GHC
libraries don't lay claim to valuable names in the linker's
namespace. I've checked in a change to the current
sources to avoid this problem for the routines below.
Assuming the duplicate entry points really do refer to
the same impl of MD5, here's what you can do:
- locate the archive libHSutil_cbits.a
- extract the md5.o object file, i.e.,
foo$ ar x /path/to/libHSutil_cbits.a md5.o
- give the md5.o object file on the command-line
when linking.
--sigbjorn
----- Original Message -----
From: "Chen Yu"
hi, there i am compiling ghc with a c library doing cryptology. however i notic there are conflicts on the definitions of these functions:
MD5Init MD5Update MD5Final
is there any way to remove them from ghc? many thanks!
------ regards, chenyu
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users