From: Robert Pluim <rpluim@gmail.com>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: emacs-devel@gnu.org
Subject: Re: FreeBSD configure error related to liblockfile
Date: Mon, 19 Feb 2018 11:43:38 +0100 [thread overview]
Message-ID: <87lgfpcl9h.fsf@gmail.com> (raw)
In-Reply-To: <86y3jrr4yp.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Sat, 17 Feb 2018 11:49:50 -0400")
Joseph Mingrone <jrm@ftfl.ca> writes:
> Hi,
>
> Configure error:
> - liblockfile package installed and `configure --without-x`
>
> checking for maillock in -lmail... no
> checking for maillock in -llockfile... no
> checking for liblockfile.so... yes
> configure: error: Shared liblockfile found but can't link against it.
> This probably means that movemail could lose mail.
> There may be a 'development' package to install containing liblockfile.
>
Could you show us the config.log corresponding to this error? And tell
us which version of Emacs you're building?
> No configure error:
> - liblockfile package not installed
> - liblockfile package installed and `configure` (no arguments)
> - liblockfile and GNU mailutils packages installed
>
> What do you recommend for the package?
>
> 1. We could just add ac_cv_prog_liblockfile=no to the configure environment.
> 2. We could add a dependency on GNU mailutils.
> 3. We could add an option to depend on GNU mailutils. If that option is turned off, then add ac_cv_prog_liblockfile=no to the configure environment.
> 4. Another approach I am missing.
The fact that this happens only when using '--without-x' indicates to
me that there might be a bug in our configure script which we should
attempt to fix.
Robert
next prev parent reply other threads:[~2018-02-19 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 15:49 FreeBSD configure error related to liblockfile Joseph Mingrone
2018-02-19 10:43 ` Robert Pluim [this message]
2018-02-19 16:19 ` Joseph Mingrone
2018-02-19 18:09 ` Paul Eggert
2018-02-19 21:50 ` Joseph Mingrone
2018-02-21 0:52 ` Joseph Mingrone
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=87lgfpcl9h.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jrm@ftfl.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.