I realised that I'd not rebuilt geany-plugins since my last upgrade and I was missing my TODO list! I downloaded the latest release and tried that, but got an error when building (From memory, the same as I'm getting now). I then grabbed the svn and tried that. The result is below.
Geany version is 0.20 (svn >= r5339). Geany-plugins is the svn as of 28/10/2010 16h14 CEST. ./autogen.sh completed happily (some macro warnings at the start, but seemed to complete since configure was run). Running ./configure doesn't throw up any errors. System is Fedora 12 with few alterations (geany being an obvious exception). gcc 4.4.4
The problem appears to be related to the PLUGIN_SET_TRANSLATABLE_INFO macro (That's where the first error crops up).
Any ideas?
Trace follows:
******************************
[jon@jon-laptop geany-plugins]$ make make all-recursive make[1]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins' Making all in po make[2]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins/po' Making all in addons make[2]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins/addons' Making all in src make[3]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins/addons/src' CC addons.lo addons.c:45: error: expected declaration specifiers or ‘...’ before string constant addons.c:46: error: expected declaration specifiers or ‘...’ before string constant addons.c:47: error: expected declaration specifiers or ‘...’ before ‘(’ token addons.c:48: error: expected declaration specifiers or ‘...’ before ‘(’ token addons.c:49: error: expected declaration specifiers or ‘...’ before string constant addons.c:50: error: expected declaration specifiers or ‘...’ before string constant addons.c: In function ‘PLUGIN_SET_TRANSLATABLE_INFO’: addons.c:54: warning: empty declaration addons.c:88: error: storage class specified for parameter ‘AddonsInfo’ addons.c:89: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token addons.c:94: error: storage class specified for parameter ‘ao_update_editor_menu_cb’ addons.c:95: error: storage class specified for parameter ‘ao_document_activate_cb’ addons.c:96: error: storage class specified for parameter ‘ao_document_open_cb’ addons.c:97: error: storage class specified for parameter ‘ao_document_save_cb’ addons.c:98: error: storage class specified for parameter ‘ao_document_before_save_cb’ addons.c:99: error: storage class specified for parameter ‘ao_document_close_cb’ addons.c:100: error: storage class specified for parameter ‘ao_startup_complete_cb’ addons.c:106: error: parameter ‘plugin_callbacks’ is initialized addons.c:108: warning: braces around scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:108: warning: initialization from incompatible pointer type addons.c:108: warning: excess elements in scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:108: warning: excess elements in scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:108: warning: excess elements in scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: braces around scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: initialization from incompatible pointer type addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: braces around scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: initialization from incompatible pointer type addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: braces around scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: initialization from incompatible pointer type addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: braces around scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: initialization from incompatible pointer type addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: braces around scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: initialization from incompatible pointer type addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: braces around scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: initialization from incompatible pointer type addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: braces around scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: initialization from incompatible pointer type addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: braces around scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:123: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:129: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:135: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:141: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:146: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:155: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:165: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:173: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:182: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:190: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:198: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:206: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:214: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:225: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:282: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:291: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:369: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:481: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:106: error: declaration for parameter ‘plugin_callbacks’ but no such parameter addons.c:102: error: declaration for parameter ‘ao_editor_notify_cb’ but no such parameter addons.c:100: error: declaration for parameter ‘ao_startup_complete_cb’ but no such parameter addons.c:99: error: declaration for parameter ‘ao_document_close_cb’ but no such parameter addons.c:98: error: declaration for parameter ‘ao_document_before_save_cb’ but no such parameter addons.c:97: error: declaration for parameter ‘ao_document_save_cb’ but no such parameter addons.c:96: error: declaration for parameter ‘ao_document_open_cb’ but no such parameter addons.c:95: error: declaration for parameter ‘ao_document_activate_cb’ but no such parameter addons.c:93: error: declaration for parameter ‘ao_update_editor_menu_cb’ but no such parameter addons.c:88: error: declaration for parameter ‘AddonsInfo’ but no such parameter addons.c:494: error: expected ‘{’ at end of input make[3]: *** [addons.lo] Error 1 make[3]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins/addons/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins/addons' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins' make: *** [all] Error 2
On Thu, 28 Oct 2010 16:17:46 +0200 Jon Senior jon@restlesslemon.co.uk wrote:
I realised that I'd not rebuilt geany-plugins since my last upgrade and I was missing my TODO list! I downloaded the latest release and tried that, but got an error when building (From memory, the same as I'm getting now). I then grabbed the svn and tried that. The result is below.
Geany version is 0.20 (svn >= r5339). Geany-plugins is the svn as of 28/10/2010 16h14 CEST. ./autogen.sh completed happily (some macro warnings at the start, but seemed to complete since configure was run). Running ./configure doesn't throw up any errors. System is Fedora 12 with few alterations (geany being an obvious exception). gcc 4.4.4
The problem appears to be related to the PLUGIN_SET_TRANSLATABLE_INFO macro (That's where the first error crops up).
Can you please put in the output of configure or ./waf configure of for the plugins?
Cheers, Frank
On Thu, 28 Oct 2010 17:59:03 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Can you please put in the output of configure or ./waf configure of for the plugins?
Attached as file. Hope that's OK. I used ./configure >> config.out and nothing was printed to the terminal, so no output on stderr.
I did just discover that I actually had an older installation of geany still on the system (in /usr/bin) and that my update earlier today had installed itself to /usr/local/bin. The result of running make is attached as make.out.
Jon
On Thu, 28 Oct 2010 18:21:20 +0200 Jon Senior jon@restlesslemon.co.uk wrote:
Attached as file. Hope that's OK. I used ./configure >> config.out and nothing was printed to the terminal, so no output on stderr.
I did just discover that I actually had an older installation of geany still on the system (in /usr/bin) and that my update earlier today had installed itself to /usr/local/bin. The result of running make is attached as make.out.
OK. Ignore last... sorry. It looks like I'd managed to end up with a set of bizarrely interlinked installations of geany. My new install in /usr was referencing files in /usr/local (I removed the old one and lost all the syntax highlighting and the fold icons turned into black blocks!). I've cleaned off all the installs, done a complete make clean; make; make install of geany and I can now build the plugins.
My bad. Sorry. Should have looked harder.
Jon
On Thu, 28 Oct 2010 18:38:10 +0200 Jon Senior jon@restlesslemon.co.uk wrote:
I did just discover that I actually had an older installation of geany still on the system (in /usr/bin) and that my update earlier today had installed itself to /usr/local/bin. The result of running make is attached as make.out.
OK. Ignore last... sorry. It looks like I'd managed to end up with a set of bizarrely interlinked installations of geany. My new install in /usr was referencing files in /usr/local (I removed the old one and lost all the syntax highlighting and the fold icons turned into black blocks!). I've cleaned off all the installs, done a complete make clean; make; make install of geany and I can now build the plugins.
My bad. Sorry. Should have looked harder.
No problem, glad you solved the problem.
I've just made geany-plugins SVN depend on Geany SVN, not 0.19. So hopefully anyone else with a similar problem would get an error message about an out of date Geany.
Nick
On Thu, 28 Oct 2010 17:58:32 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Thu, 28 Oct 2010 18:38:10 +0200 Jon Senior jon@restlesslemon.co.uk wrote:
I did just discover that I actually had an older installation of geany still on the system (in /usr/bin) and that my update earlier today had installed itself to /usr/local/bin. The result of running make is attached as make.out.
OK. Ignore last... sorry. It looks like I'd managed to end up with a set of bizarrely interlinked installations of geany. My new install in /usr was referencing files in /usr/local (I removed the old one and lost all the syntax highlighting and the fold icons turned into black blocks!). I've cleaned off all the installs, done a complete make clean; make; make install of geany and I can now build the plugins.
My bad. Sorry. Should have looked harder.
No problem, glad you solved the problem.
I've just made geany-plugins SVN depend on Geany SVN, not 0.19. So hopefully anyone else with a similar problem would get an error message about an out of date Geany.
Good thing. Thanks.
Cheers, Frank
Le 28/10/2010 16:17, Jon Senior a écrit :
[...]
The problem appears to be related to the PLUGIN_SET_TRANSLATABLE_INFO macro (That's where the first error crops up).
I'm a bit doubtful about this macro creating the problem, but I've two modifications I suggest to apply to this macro. First, to be consistent with PLUGIN_SET_INFO, add a prototype. Secondly -- event though I think I remember I wrote the original patch --, I suggest to add parentheses around the arguments of main_locale_init(), as judiciously done for all other macro parameters.
So here's a little tiny patch joined.
Regards, Colomban
On Thu, 28 Oct 2010 18:18:25 +0200 Colomban Wendling lists.ban@herbesfolles.org wrote:
The problem appears to be related to the PLUGIN_SET_TRANSLATABLE_INFO macro (That's where the first error crops up).
I'm a bit doubtful about this macro creating the problem, but I've two modifications I suggest to apply to this macro. First, to be consistent with PLUGIN_SET_INFO, add a prototype. Secondly -- event though I think I remember I wrote the original patch --, I suggest to add parentheses around the arguments of main_locale_init(), as judiciously done for all other macro parameters.
So here's a little tiny patch joined.
Thanks, applied but moved the function prototypes out of macro definitions. Should work the same.
Nick