From: Ken Brown <kbrown@cornell.edu>
To: 7435@debbugs.gnu.org
Subject: bug#7435: Trunk won't compile after change to strftime.c
Date: Thu, 18 Nov 2010 10:59:58 -0500 [thread overview]
Message-ID: <4CE54D7E.9040901@cornell.edu> (raw)
Attempting to build from the trunk as of r102429 fails on Cygwin as follows:
gcc -c -Demacs -DHAVE_CONFIG_H -I. -I/d/downloads/emacs/test/src
-D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12
-I/usr/include/freetype2 -fopenmp -I/usr/include/ImageMagick
-I/usr/include/libxml2 -I/usr/include/dbus-1.0
-I/usr/lib/dbus-1.0/include -MMD -MF deps/strftime.d
-Wimplicit-function-declaration -Wold-style-definition
-Wdeclaration-after-statement -Wno-pointer-sign -g -O2 strftime.c
strftime.c:58: warning: ‘_tzname’ redeclared without dllimport
attribute: previous dllimport ignored
strftime.c: In function ‘my_strftime_gmtime_r’:
strftime.c:187: warning: old-style function definition
strftime.c: In function ‘my_strftime_localtime_r’:
strftime.c:200: warning: old-style function definition
strftime.c: In function ‘ftime_tm_diff’:
strftime.c:388: warning: old-style function definition
strftime.c: In function ‘nstrftime’:
strftime.c:482: error: expected declaration specifiers before ‘,’ token
strftime.c:502: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘{’ token
strftime.c:1454: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘{’ token
strftime.c:1458: warning: old-style function definition
strftime.c:1456: error: expected ‘{’ at end of input
next reply other threads:[~2010-11-18 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 15:59 Ken Brown [this message]
2010-11-18 23:38 ` bug#7435: Trunk won't compile after change to strftime.c 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=4CE54D7E.9040901@cornell.edu \
--to=kbrown@cornell.edu \
--cc=7435@debbugs.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.