Plugins GTK 2.8 build test failed at: waf build
See http://nightly.geany.org/misc/build_gtk28_plugins_stderr.log for details.
Last error message: ../../gtk28_test_plugins/addons/src/addons.c:129: error: expected ')' before '*' token ../../gtk28_test_plugins/addons/src/addons.c:176: error: expected declaration specifiers before 'GtkWidget' ../../gtk28_test_plugins/addons/src/addons.c:215:24: error: missing binary operator before token "(" ../../gtk28_test_plugins/addons/src/addons.c:224: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ../../gtk28_test_plugins/addons/src/addons.c:233: error: expected '{' at end of input Build failed -> task failed (err #1): {task: cc addons.c -> addons_1.o}
On Fri, 17 Jul 2009 05:48:41 +0200 (CEST), nightly.geany.org wrote:
Plugins GTK 2.8 build test failed at: waf build
See http://nightly.geany.org/misc/build_gtk28_plugins_stderr.log for details.
Last error message: ../../gtk28_test_plugins/addons/src/addons.c:129: error: expected ')' before '*' token ../../gtk28_test_plugins/addons/src/addons.c:176: error: expected declaration specifiers before 'GtkWidget' ../../gtk28_test_plugins/addons/src/addons.c:215:24: error: missing binary operator before token "(" ../../gtk28_test_plugins/addons/src/addons.c:224: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ../../gtk28_test_plugins/addons/src/addons.c:233: error: expected '{' at end of input Build failed -> task failed (err #1): {task: cc addons.c -> addons_1.o}
Don't worry about this error and the previous sent build error mail. These are false-positives because the the geanyplugin.h header file wasn't installed yet on the build system, fixed now.
Regards, Enrico
Enrico Tröger schrieb:
On Fri, 17 Jul 2009 05:48:41 +0200 (CEST), nightly.geany.org wrote:
Plugins GTK 2.8 build test failed at: waf build
See http://nightly.geany.org/misc/build_gtk28_plugins_stderr.log for details.
Last error message: ../../gtk28_test_plugins/addons/src/addons.c:129: error: expected ')' before '*' token ../../gtk28_test_plugins/addons/src/addons.c:176: error: expected declaration specifiers before 'GtkWidget' ../../gtk28_test_plugins/addons/src/addons.c:215:24: error: missing binary operator before token "(" ../../gtk28_test_plugins/addons/src/addons.c:224: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ../../gtk28_test_plugins/addons/src/addons.c:233: error: expected '{' at end of input Build failed -> task failed (err #1): {task: cc addons.c -> addons_1.o}
Don't worry about this error and the previous sent build error mail. These are false-positives because the the geanyplugin.h header file wasn't installed yet on the build system, fixed now.
Regards, Enrico
I'm wondering if a seperate ML could be setup for those build errors. They're slightly annoying :(
Best regards.
On Fri, 17 Jul 2009 19:00:32 +0200, Thomas wrote:
Enrico Tröger schrieb:
On Fri, 17 Jul 2009 05:48:41 +0200 (CEST), nightly.geany.org wrote:
Plugins GTK 2.8 build test failed at: waf build
See http://nightly.geany.org/misc/build_gtk28_plugins_stderr.log for details.
Last error message: ../../gtk28_test_plugins/addons/src/addons.c:129: error: expected ')' before '*' token ../../gtk28_test_plugins/addons/src/addons.c:176: error: expected declaration specifiers before 'GtkWidget' ../../gtk28_test_plugins/addons/src/addons.c:215:24: error: missing binary operator before token "(" ../../gtk28_test_plugins/addons/src/addons.c:224: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ../../gtk28_test_plugins/addons/src/addons.c:233: error: expected '{' at end of input Build failed -> task failed (err #1): {task: cc addons.c -> addons_1.o}
Don't worry about this error and the previous sent build error mail. These are false-positives because the the geanyplugin.h header file wasn't installed yet on the build system, fixed now.
Regards, Enrico
I'm wondering if a seperate ML could be setup for those build errors. They're slightly annoying :(
Hehe. In general, you shouldn't see them at all :). But yes, it might be annoying. We could send the error mails to the commit mailing list, this might be a better target.
Any objections?
Regards, Enrico
On Fri, 17 Jul 2009 19:03:30 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
I'm wondering if a seperate ML could be setup for those build errors. They're slightly annoying :(
Hehe. In general, you shouldn't see them at all :). But yes, it might be annoying. We could send the error mails to the commit mailing list, this might be a better target.
Sounds OK to me. I suppose they're only really useful for committers.
Regards, Nick
On Mon, 20 Jul 2009 13:38:26 +0100, Nick wrote:
On Fri, 17 Jul 2009 19:03:30 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
I'm wondering if a seperate ML could be setup for those build errors. They're slightly annoying :(
Hehe. In general, you shouldn't see them at all :). But yes, it might be annoying. We could send the error mails to the commit mailing list, this might be a better target.
Sounds OK to me. I suppose they're only really useful for committers.
Alright. Future build failure notices are sent to geany-commits@uvena.de.
Regards, Enrico
On Mon, 20 Jul 2009 23:21:21 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
On Mon, 20 Jul 2009 13:38:26 +0100, Nick wrote:
On Fri, 17 Jul 2009 19:03:30 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
I'm wondering if a seperate ML could be setup for those build errors. They're slightly annoying :(
Hehe. In general, you shouldn't see them at all :). But yes, it might be annoying. We could send the error mails to the commit mailing list, this might be a better target.
Sounds OK to me. I suppose they're only really useful for committers.
Alright. Future build failure notices are sent to geany-commits@uvena.de.
Thanks. Great thing.
On Mon, 20 Jul 2009 23:21:21 +0200, Enrico wrote:
On Mon, 20 Jul 2009 13:38:26 +0100, Nick wrote:
On Fri, 17 Jul 2009 19:03:30 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
I'm wondering if a seperate ML could be setup for those build errors. They're slightly annoying :(
Hehe. In general, you shouldn't see them at all :). But yes, it might be annoying. We could send the error mails to the commit mailing list, this might be a better target.
Sounds OK to me. I suppose they're only really useful for committers.
Alright. Future build failure notices are sent to geany-commits@uvena.de.
Little update of the nightly build service:
- yesterday I moved the service to a new server which is more powerful and much more reliable than the old one (there were serious connectivity issues lately)
- the new server runs on an 64bit platform, so the generated Debian packages are now built for amd64 (sorry i386 users)
- the build error mails are sent to the geany commits list or the to geany-plugins commits list respective in which code the error occurred
Regards, Enrico
On Sat, 29 Aug 2009 12:55:12 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
- yesterday I moved the service to a new server which is more powerful
and much more reliable than the old one (there were serious connectivity issues lately)
Great :)
- the build error mails are sent to the geany commits list or the to
geany-plugins commits list respective in which code the error occurred
Nice, so plugin authors can easily see any errors introduced.
Regards, Nick