Peter van Dijk writes:
> I've written software in C that compiled cleanly on my Slackware, on LinuxPPC and
> others, but not on RedHat. It turns out it needed -lcrypt. Does _not_ make sense to
> me.
You can make the same argument the other way. There is no formal set of
specifications as to what library contains which functions, at least under
Linux.
My sqwebmail CGI client will happily compile with shadow password support
on both Slackware and Red Hat boxes, with or without crypt() in a separate
library. This is a non issue. Apart from a few lines in a configuration
file, I don't really lose much sleep over it. I don't care much for
religious wars (well, most religious wars), so I just stick the lone macro
into configure.in, and move on to something else.
--
Sam
