public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org> To: nobody@sourceware.cygnus.com Cc: gnats-prs@sourceware.cygnus.com Subject: Re: gnats/200: gnatsd.h includes <crypt.h> for crypt(3) rather than <unistd.h> Date: Sun, 10 Jun 2001 10:34:00 -0000 [thread overview] Message-ID: <20010610173400.8877.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR gnats/200; it has been noted by GNATS. From: Milan Zamazal <pdm@zamazal.org> To: soren@wheel.dk Cc: gnats-gnats@sourceware.cygnus.com Subject: Re: gnats/200: gnatsd.h includes <crypt.h> for crypt(3) rather than <unistd.h> Date: 10 Jun 2001 17:25:41 +0200 >>>>> "s" == soren <soren@wheel.dk> writes: s> <crypt.h> is a little outdated, and modern systems specify s> <unistd.h> for crypt(3). E.g. *BSD don't have <crypt.h>. [...] >> Fix: s> Index: gnatsd.c s> =================================================================== s> RCS file: /cvs/gnats/gnats/gnats/gnatsd.c,v s> retrieving revision 1.40 s> diff -u -w -r1.40 gnatsd.c s> --- gnatsd.c 2001/04/15 18:11:51 1.40 s> +++ gnatsd.c 2001/05/31 15:26:03 s> @@ -24,9 +24,7 @@ s> #include "gnatsd.h" s> #include "query.h" s> -#ifdef HAVE_LIBCRYPT s> -#include <crypt.h> s> -#endif s> +#include <unistd.h> s> #if defined (__svr4__) && defined (__sun__) s> #undef SIG_IGN Well, GNATS should run on less modern systems too, so I now include crypt.h only if available. That should fix the build problems on systems having crypt in unistd.h. Thanks for the report. Regards, Milan Zamazal -- http://www.zamazal.org
next reply other threads:[~2001-06-10 10:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-10 10:34 Milan Zamazal [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-30 12:07 pdm 2001-05-31 8:34 soren
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010610173400.8877.qmail@sourceware.cygnus.com \ --to=pdm@zamazal.org \ --cc=gnats-prs@sourceware.cygnus.com \ --cc=nobody@sourceware.cygnus.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).