On Mon, Mar 22, 1999 at 11:38:49PM +0000, Sam wrote:
> Peter van Dijk writes:
>
> > Your errno.h is broken.. on my system, it's in /usr/include, there it includes
> > /usr/include/linux/errno.h which includes /usr/include/sys/errno.h
> >
> > I'm starting to get used to RedHat being broken (happily running slackware here :),
> > so this is not surprising to me :)
>
> Red Hat is not broken. The individual in question broke Red Hat by shoving
> kernel 2.2 in there, breaking something in the process.
umm yeah it is broken. At least, I consider it broken [to wit, last time I told that
on a mailinglist the first person to respond pointed out that RH is DOA, not
defective :)]
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.
> P.S. Actually, linux/errno.h includes asm/errno.h, with asm being a soft
> link to /usr/src/linux/include/asm, which contains the real errno.h to
> match the current running kernel (which hasn't changed much, over the
> lifetime of the 2.0 kernel).
>
> #include <errno.h>
>
> always worked for me...
And it should.
Greetz, Peter.
--
.| Peter van Dijk | <mo|VERWEG> stoned worden of coden
.| [EMAIL PROTECTED] | <mo|VERWEG> dat is de levensvraag
| <mo|VERWEG> coden of stoned worden
| <mo|VERWEG> stonend worden En coden
| <mo|VERWEG> hmm
| <mo|VERWEG> dan maar stoned worden en slashdot lezen:)
