Doesnt build on armel yet, but i think its a problem in base libs rather than libgwibber because previous version worked.
There are a bunch of warnings in the build log that should be looked into: 1. no return in non-void func: entry.c:792: warning: no return statement in function returning non-void 2. "... may be used uninitialized in this function" warnings; most if not all are in generated code, so might be OK or a bug in generator: service.c:1582: warning: '_edomain' may be used uninitialized in this function service.c:1583: warning: '_ecode' may be used uninitialized in this function service.c:1477: warning: '_edomain' may be used uninitialized in this function service.c:1478: warning: '_ecode' may be used uninitialized in this function service.c:1372: warning: '_edomain' may be used uninitialized in this function service.c:1373: warning: '_ecode' may be used uninitialized in this function service.c:2019: warning: '_edomain' may be used uninitialized in this function service.c:2020: warning: '_ecode' may be used uninitialized in this function service.c:1908: warning: '_edomain' may be used uninitialized in this function service.c:1909: warning: '_ecode' may be used uninitialized in this function service.c:1797: warning: '_edomain' may be used uninitialized in this function service.c:1798: warning: '_ecode' may be used uninitialized in this function service.c:1690: warning: '_edomain' may be used uninitialized in this function service.c:1691: warning: '_ecode' may be used uninitialized in this function service.c:835: warning: 'reply' may be used uninitialized in this function service.c:700: warning: 'reply' may be used uninitialized in this function service.c:568: warning: 'reply' may be used uninitialized in this function service.c:438: warning: 'reply' may be used uninitialized in this function service.c:308: warning: 'reply' may be used uninitialized in this function accounts.c:1148: warning: '_edomain' may be used uninitialized in this function accounts.c:1149: warning: '_ecode' may be used uninitialized in this function accounts.c:1036: warning: '_edomain' may be used uninitialized in this function accounts.c:1037: warning: '_ecode' may be used uninitialized in this function accounts.c:922: warning: '_edomain' may be used uninitialized in this function accounts.c:923: warning: '_ecode' may be used uninitialized in this function accounts.c:275: warning: 'reply' may be used uninitialized in this function urlshorten.c:503: warning: '_edomain' may be used uninitialized in this function urlshorten.c:504: warning: '_ecode' may be used uninitialized in this function connection.c:555: warning: '_edomain' may be used uninitialized in this function connection.c:556: warning: '_ecode' may be used uninitialized in this function streams.c:519: warning: '_edomain' may be used uninitialized in this function streams.c:520: warning: '_ecode' may be used uninitialized in this function please fix 1. and review 2. for sanity. At least a few look really not right. -- [MIR] libgwibber https://bugs.launchpad.net/bugs/618757 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
