Peter van Dijk <[EMAIL PROTECTED]> 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.
Umm... I don't mean to sound harsh here, but this is one of the most
common portability differences between Unixes. Pretty much anyone writing
Unix code that uses crypt() has to deal with at some point or another.
You can blame this one on the U.S. Government's idiotic export
restrictions; that's the original reason why crypt() was spun off into a
separate library on some Unixes (and not on others).
Any portable Unix code that needs to use crypt() should be able to deal
with the possible need to link with -lcrypt. autoconf makes this pretty
trivial.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
