eclipse version 3.5.2-8ubuntu3 failed to build on i386

[Matthias Klose]

eclipse version 3.5.2-8ubuntu3 failed to build on i386
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/+buildjob/2391700

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/+buildjob/2391700/+files/buildlog_ubuntu-natty-i386.eclipse_3.5.2-8ubuntu3_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 9011 lines into the build log:

     [exec] make[1]: Leaving directory `/build/buildd/eclipse-3.5.2/build/eclipse-3.5.2-src/plugins/org.eclipse.core.filesystem/natives/unix/linux'
     [move] Moving 1 file to /build/buildd/eclipse-3.5.2/build/eclipse-3.5.2-src/plugins/org.eclipse.core.filesystem.linux.x86/os/linux/x86
     [echo] uname -m: i686. Build eclipse on x86 for x86.

compile.libgnomeproxy:
     [exec] make[1]: Entering directory `/build/buildd/eclipse-3.5.2/build/eclipse-3.5.2-src/plugins/org.eclipse.core.net/natives/unix/linux'
     [exec] Building file: gnomeproxy.o
     [exec] Invoking: GCC C Compiler
     [exec] gcc -I/usr/include/gconf/2/ -I/usr/include/orbit-2.0/ -I/usr/include/glib-2.0/ -I/usr/lib/glib-2.0/include/ -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux -O0 -fPIC -g3 -Wall -c -fmessage-length=0 -m32 -o gnomeproxy.o ../gnomeproxy.c
     [exec] make[1]: Leaving directory `/build/buildd/eclipse-3.5.2/build/eclipse-3.5.2-src/plugins/org.eclipse.core.net/natives/unix/linux'
     [exec] In file included from /usr/include/glib-2.0/glib/galloca.h:34:0,
     [exec] from /usr/include/glib-2.0/glib.h:32,
     [exec] from ../gnomeproxy.c:15:
     [exec] /usr/include/glib-2.0/glib/gtypes.h:34:24: fatal error: glibconfig.h: No such file or directory
     [exec] compilation terminated.
     [exec] make[1]: *** [compile] Error 1

BUILD FAILED
/build/buildd/eclipse-3.5.2/build.xml:516: The following error occurred while executing this line:
/build/buildd/eclipse-3.5.2/build.xml:481: exec returned: 2

Total time: 3 minutes 44 seconds
dh_auto_build: ant returned exit code 1
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110403-1050
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/eclipse-3.5.2

[Anders Kaseorg (andersk)]

eclipse 3.5.2-10ubuntu1 failed to build in the same way on oneiric.

[Anders Kaseorg (andersk)]

Here’s a patch, tested in https://launchpad.net/~anders-kaseorg/+archive/ppa .

[Benjamin Drung (bdrung)]

Thanks for the patch. Will you forward the gnomeproxy-pkg-config.patch to upstream too?

[Launchpad Janitor (janitor)]

This bug was fixed in the package eclipse - 3.5.2-10ubuntu2

---------------
eclipse (3.5.2-10ubuntu2) oneiric; urgency=low

  * debian/patches/gnomeproxy-makefile.patch: Set Java include path for
    libgnomeproxy.
  * debian/patches/gnomeproxy-pkg-config.patch: Use pkg-config to find
    include files and libraries for libgnomeproxy. (LP: #749218)
 -- Anders Kaseorg <email address hidden> Thu, 26 May 2011 22:19:59 +0200

[Anders Kaseorg (andersk)]

Build Identifier:

Some of the GLib include files have moved on Ubuntu for the multiarch transition. This isn’t supposed to break anything because the paths are exported via pkg-config, but libgnomeproxy ignores pkg-config and hard-codes the old pahts. I had to add this patch to org.eclipse.core.net to make Eclipse compile on Ubuntu oneiric i386.

Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/749218

Reproducible: Always

[Anders Kaseorg (andersk)]

Created attachment 197289
[PATCH] Use pkg-config to find include files and libraries for libgnomeproxy

[Anders Kaseorg (andersk)]

I sent the patch to https://bugs.eclipse.org/bugs/show_bug.cgi?id=348165 .

[Lars-vogel-d (lars-vogel-d)]

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.