Sure, makes sense. Just to clarify: usually these symbols shouldn't even be exported by the library, but I guess the linker may not support this on some platforms, so the change still makes sense.
Fixed in Git bf7c90c3..603ecd85 Happy hacking! Christian On 6/3/19 9:20 AM, [email protected] wrote: > Hi to all. > > I updated to the latest version 0.9.63. > This version caused some trouble with duplicated symbols in the newly > introduced hash methods sha256_init and sha256_update. > I want to ask if it is possible to use unique (MHD specific) names for > them? > > I attached a patch that introduce MHD_* as a preamble for the functions. > To have a consistent name convention, I also renamed the MD5 hash > functions. > > It would be great for the compatibilty with other hashing libraries if > this suggestion could be applied. > > Kind regards, > Dirk Brinkmeier. > >
signature.asc
Description: OpenPGP digital signature
