A test in pbuilder shows that this is only the tip of the iceberg. Even
after applying the patch, we get this:
cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../libplanner -I.. -I../libplanner
-pthread -DORBIT2=1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/libxml2 -I/usr/include/gnome-vfs-2.0
-I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2
-I/usr/include/orbit-2.0
-DSTORAGEMODULEDIR=\"/usr/lib/planner/storage-modules\"
-DFILEMODULEDIR=\"/usr/lib/planner/file-modules\"
-DPLUGINDIR=\"/usr/lib/planner/plugins\" -DDATADIR=\"/usr/share\"
-I/usr/include/libgda-3.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/libxml2 -DGDA_VERSION=30 -g -O2 -g -Wall -O2 -c mrp-sql.c -fPIC
-DPIC -o .libs/libstorage_sql_la-mrp-sql.o
mrp-sql.c: In function 'sql_write_project':
mrp-sql.c:2449: error: expected ')' before ';' token
mrp-sql.c:2455: error: expected ')' before ';' token
mrp-sql.c:2477: error: expected ')' before ';' token
mrp-sql.c:2538: error: expected ')' before ';' token
mrp-sql.c: In function 'mrp_sql_save_project':
mrp-sql.c:3726: error: expected ')' before ';' token
make[3]: *** [libstorage_sql_la-mrp-sql.lo] Error 1
make[3]: Leaving directory `/tmp/buildd/planner-0.14.3/libplanner'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/planner-0.14.3'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/planner-0.14.3'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
pbuilder: Failed autobuilding of package
W: no hooks of type C found -- ignoring
-> Aborting with an error
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /var/cache/pbuilder/build//8822 and its subdirectories
What amazes me is that this previously built fine as-is, as attested by
the Debian buildd logs. I'm thus wondering whether older GCC missed
this and why.
--
please sync planner (main) from Debian (main)
https://bugs.launchpad.net/bugs/219109
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
