From: Daniel Colascione <dancol@dancol.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Is the Cygw32 port ready for testing?
Date: Mon, 15 Oct 2012 14:36:42 -0700 [thread overview]
Message-ID: <507C81EA.1000502@dancol.org> (raw)
In-Reply-To: <507C8180.8010601@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
On 10/15/2012 2:34 PM, Ken Brown wrote:
> On 10/15/2012 5:31 PM, Daniel Colascione wrote:
>> Emacs builds and starts fine for me even when dbus-daemon is running, with or
>> without X also running. Running dbus-monitor doesn't report anything happening.
>> A stack trace from your environment would be helpful.
>
> OK. It will probably be a week or so before I can do this, but there's a slight
> chance I'll get to it sooner. Did you definitely build emacs with dbus
> support? You need to have libdbus1-devel installed in order for this to happen.
$ ldd emacs.exe
ntdll.dll => /Windows/SysWOW64/ntdll.dll (0x7de70000)
kernel32.dll => /Windows/syswow64/kernel32.dll (0x7dd60000)
KERNELBASE.dll => /Windows/syswow64/KERNELBASE.dll (0x7d850000)
cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
cygdbus-1-3.dll => /usr/bin/cygdbus-1-3.dll (0xc4140000)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cyggif-4.dll => /usr/bin/cyggif-4.dll (0xc3900000)
...
Could you describe your test environment?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-10-15 21:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 22:44 Is the Cygw32 port ready for testing? Ken Brown
2012-10-14 23:28 ` Daniel Colascione
2012-10-15 1:16 ` Ken Brown
2012-10-15 1:31 ` Ken Brown
2012-10-15 1:34 ` Daniel Colascione
2012-10-15 1:37 ` Daniel Colascione
2012-10-15 7:34 ` Andreas Schwab
2012-10-15 14:14 ` Ken Brown
2012-10-15 17:16 ` Eli Zaretskii
2012-10-15 19:33 ` Ken Brown
2012-10-15 19:35 ` Daniel Colascione
2012-10-15 21:31 ` Daniel Colascione
2012-10-15 21:34 ` Ken Brown
2012-10-15 21:36 ` Daniel Colascione [this message]
2012-10-16 13:23 ` Ken Brown
2012-10-16 18:24 ` Eli Zaretskii
2012-10-17 4:13 ` Stephen J. Turnbull
2012-10-17 15:42 ` Eli Zaretskii
2012-10-17 17:36 ` Stephen J. Turnbull
2012-10-17 23:45 ` Nix
2012-10-18 12:28 ` Ken Brown
2012-10-18 17:02 ` Daniel Colascione
2012-10-18 22:18 ` Ken Brown
2012-10-18 17:09 ` Eli Zaretskii
2012-10-18 22:04 ` Stefan Monnier
2012-10-19 6:43 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2012-10-19 16:03 Angelo Graziosi
2012-10-20 2:42 ` Ken Brown
2012-10-20 2:49 ` Daniel Colascione
2012-10-20 6:53 ` Andreas Schwab
2012-10-21 13:02 ` Stephen J. Turnbull
2012-10-20 8:53 ` Angelo Graziosi
2012-10-20 10:29 ` Eli Zaretskii
2012-10-20 13:19 ` Ken Brown
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=507C81EA.1000502@dancol.org \
--to=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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).