all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mike Kupfer <kupfer@rawbw.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 75004@debbugs.gnu.org
Subject: bug#75004: 30.0.92; documentation unclear about D-Bus support
Date: Sat, 21 Dec 2024 14:53:25 -0800	[thread overview]
Message-ID: <42621.1734821605@alto.camomileplus.org> (raw)
In-Reply-To: <87zfkpngys.fsf@gmx.de>

Michael Albinus wrote:

> Could you pls check, whether the appended patch (for dbus.texi and
> tramp.texi) helps?

It does.  Thanks for the fast turnaround.

> > Configured features:
> > CAIRO FREETYPE GIF GLIB GMP GNUTLS GSETTINGS HARFBUZZ JPEG LIBSELINUX
> > LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG SECCOMP SOUND THREADS TIFF
> > TOOLKIT_SCROLL_BARS WEBP X11 XDBE XIM XPM LUCID ZLIB
> 
> Hmm, DBUS is not mentioned. Per default, it should be enabled. Perhaps
> you need to install the libdbus-1-dev package on your Debian system?

Yes, that was the issue; thanks.

BTW, I was surprised that 'configure' did not error out when I supplied
--with-dbus (or --with-dbus=yes) on the command line.  I expect
'configure' to disable a feature (and exit with status 0) if the feature
can't be provided and wasn't explicitly requested, but I thought the
inability to provide a specifically requested feature was considered an
error.  Am I misunderstanding how 'configure' is supposed to work?

mike





      parent reply	other threads:[~2024-12-21 22:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21  1:08 bug#75004: 30.0.92; documentation unclear about D-Bus support Mike Kupfer
2024-12-21 16:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 16:24   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 22:53   ` Mike Kupfer [this message]

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=42621.1734821605@alto.camomileplus.org \
    --to=kupfer@rawbw.com \
    --cc=75004@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.