unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Voegele <voegelas@gmx.net>
Subject: Re: [PATCH] configure check for crypt()
Date: Thu, 19 Feb 2004 11:27:38 +0100	[thread overview]
Message-ID: <871xor4b51.fsf@ID-28718.user.uni-berlin.de> (raw)
In-Reply-To: <87eksw6s4d.fsf@ID-28718.user.uni-berlin.de> (Andreas Voegele's message of "Sun, 15 Feb 2004 20:48:50 +0100")

Andreas Voegele writes:

> Here's a patch that replaces AC_CHECK_LIB with AC_SEARCH_LIBS and
> HAVE_LIBCRYPT with HAVE_CRYPT.  I've tested this patch under HP-UX
> and GNU/Linux.

It seems that my patch is also useful for OpenBSD.  At least, I found
the following statement on the web: "With version 2.1 of OpenBSD, the
crypt library doesn't even exist; it is included in the standard
library for the system."

Can anyone apply the patch, which is attached to my previous mail, to
guile-core/configure.in and guile-core/libguile/posix.c?

Here are changelog entries for guile-core/configure.in and
guile-core/libguile/configure.in respectively:

2004-02-19  Andreas Voegele  <voegelas@gmx.net>

	* configure.in: Use AC_SEARCH_LIBS to search for crypt().  Define
	HAVE_CRYPT instead of HAVE_LIBCRYPT.

2004-02-19  Andreas Voegele  <voegelas@gmx.net>

	* posix.c (s_scm_crypt): Use HAVE_CRYPT instead of HAVE_LIBCRYPT.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-02-19 10:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 19:48 [PATCH] configure check for crypt() Andreas Voegele
2004-02-19 10:27 ` Andreas Voegele [this message]
2004-02-20 23:17   ` Kevin Ryde
2004-02-21  0:52     ` Rob Browning
2004-02-21  7:30     ` Andreas Voegele
2004-02-21 21:00       ` Kevin Ryde
2004-02-21 21:41       ` Kevin Ryde

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871xor4b51.fsf@ID-28718.user.uni-berlin.de \
    --to=voegelas@gmx.net \
    /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: link
Be 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).