wily and gcc-3.4 bug
- From: <mjr@xxxxxxxxxxxxx>
- To: <wilyfans@xxxxxxxxxxxxx>
- Date: Tue, 07 Sep 2004 00:36:51 +0100
Andreas Jochens reported this bug to me as debian packager of wily and
sent in a patch. Can this be merged into the main sources safely?
---- Begin forwarded excerpt ----
When building 'wily' with gcc-3.4 I get the following error:
win.c:458: error: parse error before "__FUNCTION__"
win.c: In function `handleWEexec':
win.c:512: error: parse error before "__FUNCTION__"
win.c:521: error: parse error before "__FUNCTION__"
win.c: In function `handleshellinput':
win.c:558: error: parse error before "__FUNCTION__"
win.c:566: error: parse error before "__FUNCTION__"
win.c: In function `handlemsg':
win.c:637: error: parse error before "__FUNCTION__"
win.c:651: error: parse error before "__FUNCTION__"
win.c: In function `openmaster':
win.c:729: error: parse error before "__FUNCTION__"
win.c: In function `openslave':
win.c:752: error: parse error before "__FUNCTION__"
win.c: In function `setslaveattr':
win.c:786: error: parse error before "__FUNCTION__"
win.c:800: error: parse error before "__FUNCTION__"
make[1]: *** [win] Error 1
make[1]: Leaving directory `/wily-0.13.41/tools/win'
make: *** [build-stamp] Error 2
With the attached patch 'wily' can be compiled using gcc-3.4.
diff -urN ../tmp-orig/wily-0.13.41/tools/win/wgoto.c ./tools/win/wgoto.c
--- ../tmp-orig/wily-0.13.41/tools/win/wgoto.c 1996-12-02 07:44:13.000000000
+0100
+++ ./tools/win/wgoto.c 2004-09-05 11:45:27.400076169 +0200
@@ -18,7 +18,7 @@
#define STRINGIZE2(x) #x
#define STRINGIZE(x) STRINGIZE2(x)
#ifdef __GNUC__
- #define here " at " __FILE__ ":" STRINGIZE(__LINE__) " in "
__FUNCTION__ "()"
+ #define here " at " __FILE__ ":" STRINGIZE(__LINE__) " in "
STRINGIZE(__FUNCTION__) "()"
#else
#define here " at " __FILE__ ":" STRINGIZE(__LINE__)
#endif
diff -urN ../tmp-orig/wily-0.13.41/tools/win/win.c ./tools/win/win.c
--- ../tmp-orig/wily-0.13.41/tools/win/win.c 1996-12-02 07:44:13.000000000
+0100
+++ ./tools/win/win.c 2004-09-05 11:45:55.598789313 +0200
@@ -65,7 +65,7 @@
#define stringize2(x) #x
#define stringize(x) stringize2(x)
#if defined(__GNUC__)
- #define here " at " __FILE__ ":" stringize(__LINE__) " in "
__FUNCTION__ "()"
+ #define here " at " __FILE__ ":" stringize(__LINE__) " in "
stringize(__FUNCTION__) "()"
#else
#define here " at " __FILE__ ":" stringize(__LINE__)
#endif
diff -urN ../tmp-orig/wily-0.13.41/tools/win/wreplace.c ./tools/win/wreplace.c
--- ../tmp-orig/wily-0.13.41/tools/win/wreplace.c 1996-12-02
07:44:13.000000000 +0100
+++ ./tools/win/wreplace.c 2004-09-05 11:46:22.837648377 +0200
@@ -18,7 +18,7 @@
#define STRINGIZE2(x) #x
#define STRINGIZE(x) STRINGIZE2(x)
#ifdef __GNUC__
- #define here " at " __FILE__ ":" STRINGIZE(__LINE__) " in "
__FUNCTION__ "()"
+ #define here " at " __FILE__ ":" STRINGIZE(__LINE__) " in "
STRINGIZE(__FUNCTION__) "()"
#else
#define here " at " __FILE__ ":" STRINGIZE(__LINE__)
#endif
--
MJR/slef My Opinion Only and not of any group I know
http://www.ttllp.co.uk/ for creative copyleft computing
Please email about: BT alternative for line rental+DSL;
Education on SMEs+EU FP6; office filing that works fast
Other related posts:
