[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gnulib] Problem with the md5 module

From: Martin Lambers
Subject: Re: [bug-gnulib] Problem with the md5 module
Date: Fri, 28 Jan 2005 15:46:04 +0100
User-agent: Mutt/1.5.6i

On Thu, 27. Jan 2005, 22:04:29 -0800, Paul Eggert wrote:
> > I use the md5 module of gnulib.
> >
> > On systems with MD5Init(), MD5Update(), MD5Final() (for example *BSD or
> > dietlibc), I would like to use these functions instead....
> >
> > Any ideas how I can do this?
> The usual solution is to distribute a file called md5_.h (which would
> be a copy of what is now gnulib/lib/md5.h), and to copy md5_.h to
> md5.h only on systems where the standard <md5.h> doesn't suffice.
> See, for example, gnulib's getopt and fnmatch modules.  Perhaps you
> can change the md5 module to do something similar; that would make
> sense.

I think this would make more sense if the gnulib md5 module used the BSD
API and thus would be a fallback for systems without these functions,
just like the getopt module is a fallback for systems without
getopt_long() and friends.
Because the md5 module uses a different API, a different header name
would be more obvious, for example gmd5.h.

As it is now, once you imported the gnulib md5 module, you cannot access
the BSD API anymore (if you don't want to make local changes to gnulib
modules). For this reason I will probably just stop using the BSD
functions and always use the gnulib module, as suggested by Simon.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]