unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: movemail on Debian
Date: 30 Apr 2003 18:59:11 +0100	[thread overview]
Message-ID: <rzqy91rx3ww.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: E19AkNT-0008EE-00@fencepost.gnu.org

Richard Stallman <rms@gnu.org> writes:

> 	    * configure.in: When we have -llockfile, define HAVE_LIBMAIL, not
> 	    LIBMAIL.
> 
> Can you explain the meaning of defining LIBMAIL,

I think there wasn't any.  [I was fairly sure the configurey worked at
one stage, but that was perhaps a couple of years back and it seems
the current version doesn't DTRT despite what the Debian patch says.]

> and the meaning of defining HAVE_LIBMAIL, so I can understand this
> change?

It's normal autoconf for `can link -lmail'.

> Does HAVE_LIBMAIL have any existing meaning, distinct from its effect
> on the conditional you are adding to gnu-linux.h?

I think movemail is written to work with function `maillock' (?) from
a proprietary libmail.  Debian has the same function in liblockfile.
Defining HAVE_LIBMAIL (albeit a lie) gets movemail to use maillock --
as I commented in gnu-linux.h -- without touching movemail.c.  See
conditionals on HAVE_LIBMAIL &c near the top of movemail.c.

Is that clear?

  reply	other threads:[~2003-04-30 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rzqissx2xrl.fsf@albion.dl.ac.uk>
2003-04-30  5:43 ` movemail on Debian Richard Stallman
2003-04-30 17:59   ` Dave Love [this message]
2003-05-02 14:37     ` Richard Stallman
2003-05-03 14:25       ` Dave Love
2003-05-04 13:04         ` Richard Stallman
2003-05-04 18:05           ` Dave Love
2003-05-05 19:10             ` Richard Stallman
2003-05-20 16:59               ` Dave Love
2003-05-21 15:31                 ` Richard Stallman
2003-05-25 15:31                   ` Dave Love

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/emacs/

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

  git send-email \
    --in-reply-to=rzqy91rx3ww.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).