From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: Windows mingw64 and cygwin builds broken Date: Fri, 13 Nov 2015 22:30:51 +0000 Message-ID: <86d1vdh6qs.fsf@gmail.com> References: <867flnrnhg.fsf@gmail.com> <83y4e3gdbb.fsf@gnu.org> <86y4e2rhom.fsf@gmail.com> <836116gt5t.fsf@gnu.org> <86a8qiyzgx.fsf@gmail.com> <83si4af2ue.fsf@gnu.org> <83k2pmez7e.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447453912 10203 80.91.229.3 (13 Nov 2015 22:31:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Nov 2015 22:31:52 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 13 23:31:43 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZxMsd-0006OI-2J for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2015 23:31:39 +0100 Original-Received: from localhost ([::1]:55563 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxMsc-0001k0-IG for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2015 17:31:38 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48080) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxMsM-0001jk-Je for emacs-devel@gnu.org; Fri, 13 Nov 2015 17:31:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxMsI-0000xP-IN for emacs-devel@gnu.org; Fri, 13 Nov 2015 17:31:22 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:53475) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxMsI-0000xJ-Bv for emacs-devel@gnu.org; Fri, 13 Nov 2015 17:31:18 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZxMs8-0005mX-Nh for emacs-devel@gnu.org; Fri, 13 Nov 2015 23:31:08 +0100 Original-Received: from 82-69-64-228.dsl.in-addr.zen.co.uk ([82.69.64.228]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 13 Nov 2015 23:31:08 +0100 Original-Received: from andrewjmoreton by 82-69-64-228.dsl.in-addr.zen.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 13 Nov 2015 23:31:08 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 82-69-64-228.dsl.in-addr.zen.co.uk User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (windows-nt) Cancel-Lock: sha1:iDXz8V669KKVsivWrl0lkM5ZeeY= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194421 Archived-At: On Fri 13 Nov 2015, Eli Zaretskii wrote: >> From: Andy Moreton >> Date: Fri, 13 Nov 2015 14:18:14 +0000 >> >> >> As users may want to use D-Bus with cygwin-w32 emacs (and possibly with >> >> mingw64 emacs), a configure option is needed for the w32-notifications. >> > >> > No, I don't think we need a configure option. The intent was to >> > provide the native w32 notifications only if D-Bus is not available, >> > because the former support only a small subset of the functionality. >> >> That still leaves users without the ability to turn both off (unless >> they patch the sources before building). > > Why would they want to? We don't let them turn, say, > w32-shell-execute off, do we? How is this feature different? > >> I've since tried the cygwin-w32 and mingw64 builds on a different >> machine, where both builds succeed (however the two machines may have >> dfferent sets of packages installed in each environment). > > Thanks. Please also see if it works on the same machine where it > failed before that. The machine with previously failing builds is now ok, so all seems to be fixed. AndyM