From: Ken Brown <kbrown@cornell.edu>
To: Daniel Colascione <dancol@dancol.org>
Cc: Emacs <emacs-devel@gnu.org>
Subject: Re: Is the Cygw32 port ready for testing?
Date: Sun, 14 Oct 2012 21:31:16 -0400 [thread overview]
Message-ID: <507B6764.5090707@cornell.edu> (raw)
In-Reply-To: <507B6404.8080103@cornell.edu>
On 10/14/2012 9:16 PM, Ken Brown wrote:
> On 10/14/2012 7:28 PM, Daniel Colascione wrote:
>> Thanks for reporting the build break. I've updated the trunk. Revision
>> 110548
>> should resolve the problem.
>
> Thanks. The build now completes as long as I use the configure option
> --without-dbus. Otherwise the build fails while compiling dbusbind.c:
>
> gcc -std=gnu99 -c -I/usr/include/noX -Demacs -I.
> -I/home/kbrown/src/emacs/test-w32/src -I../lib
> -I/home/kbrown/src/emacs/test-w32/src/../lib -I/usr/include/libxml2
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -MMD -MF
> deps/dbusbind.d -MP -I/usr/include/p11-kit-1 -g3 -O2 dbusbind.c
> dbusbind.c: In function ‘Fdbus_message_internal’:
> dbusbind.c:1263:25: error: expected ‘{’ before ‘=’ token
> dbusbind.c:1263:15: error: two or more data types in declaration specifiers
> dbusbind.c:1294:17: error: expected ‘{’ before ‘=’ token
> dbusbind.c:1318:7: error: expected ‘{’ before ‘)’ token
> dbusbind.c:1318:7: warning: type defaults to ‘int’ in type name
> dbusbind.c:1318:7: error: expected ‘{’ before ‘)’ token
> dbusbind.c:1318:7: warning: type defaults to ‘int’ in type name
> dbusbind.c:1318:7: error: expected ‘{’ before ‘)’ token
> dbusbind.c:1318:7: warning: type defaults to ‘int’ in type name
> dbusbind.c:1331:7: error: expected expression before ‘struct’
> dbusbind.c:1331:7: error: too few arguments to function ‘format2’
> lisp.h:3120:20: note: declared here
> dbusbind.c:1331:7: error: expected expression before ‘struct’
> dbusbind.c:1331:7: error: too few arguments to function ‘format2’
> lisp.h:3120:20: note: declared here
> dbusbind.c:1341:7: error: expected expression before ‘struct’
> dbusbind.c:1341:7: error: too few arguments to function ‘format2’
> lisp.h:3120:20: note: declared here
> dbusbind.c:1341:7: error: expected expression before ‘struct’
> dbusbind.c:1341:7: error: too few arguments to function ‘format2’
> lisp.h:3120:20: note: declared here
> dbusbind.c:1412:47: error: expected ‘{’ before ‘)’ token
> dbusbind.c:1412:47: warning: type defaults to ‘int’ in type name
> dbusbind.c:1412:47: error: expected ‘{’ before ‘)’ token
> dbusbind.c:1412:47: warning: type defaults to ‘int’ in type name
> dbusbind.c: In function ‘xd_read_message_1’:
> dbusbind.c:1530:30: error: expected identifier or ‘(’ before ‘struct’
> dbusbind.c:1565:13: error: expected ‘{’ before ‘=’ token
> dbusbind.c:1566:3: error: ‘member’ undeclared (first use in this function)
> dbusbind.c:1566:3: note: each undeclared identifier is reported only
> once for each function it appears in
> dbusbind.c:1568:3: error: expected expression before ‘struct’
> dbusbind.c:1602:22: error: expected ‘{’ before ‘==’ token
> dbusbind.c:1602:31: error: expected expression before ‘||’ token
> dbusbind.c:1602:31: warning: type defaults to ‘int’ in type name
> dbusbind.c:1609:25: error: expected expression before ‘struct’
> dbusbind.c:1644:33: error: expected ‘{’ before ‘==’ token
> dbusbind.c:1644:75: error: expected expression before ‘,’ token
> dbusbind.c:1644:75: warning: type defaults to ‘int’ in type name
Another thing I just noticed is that the executable depends on some of
the X11 libraries, which I don't think is what you wanted:
$ cygcheck src/emacs.exe
[...]
C:\cygwin\bin\cyggif-4.dll
C:\cygwin\bin\cyggcc_s-1.dll
C:\cygwin\bin\cygX11-6.dll
C:\cygwin\bin\cygxcb-1.dll
C:\cygwin\bin\cygXau-6.dll
C:\cygwin\bin\cygXdmcp-6.dll
[...]
next prev parent reply other threads:[~2012-10-15 1:31 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507B6764.5090707@cornell.edu \
--to=kbrown@cornell.edu \
--cc=dancol@dancol.org \
--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 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.