loqui version 0.4.4-1 failed to build on i386
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
loqui (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Unassigned |
Bug Description
loqui version 0.4.4-1 failed to build on i386
Link to failed build: https:/
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1393 lines into the build log:
appending configuration tag "F77" to libtool
checking for windres... no
checking for pkg-config... /usr/bin/pkg-config
checking for GLIB - version >= 2.4.0... yes (version 2.28.5)
checking for glib-genmarshal... /usr/bin/
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for GTK+ - version >= 2.4.0... yes (version 2.24.4)
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for GNET - version >= 2.0.0... no
*** Could not run GNET test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GNET is incorrectly installed.
configure: error: Test for GNet failed. See the 'INSTALL' for help.
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
*******
Build finished at 20110408-1817
FAILED [dpkg-buildpackage died]
Purging chroot-
Related branches
Changed in loqui (Ubuntu): | |
importance: | Undecided → High |
tags: | added: oneiric |
Changed in loqui (Ubuntu): | |
milestone: | none → oneiric-alpha-1 |
Changed in loqui (Ubuntu Oneiric): | |
milestone: | oneiric-alpha-1 → oneiric-alpha-2 |
Changed in loqui (Ubuntu Oneiric): | |
milestone: | oneiric-alpha-2 → none |
status: | New → Confirmed |
tags: | added: universe |
Part of the problem with this bug has to do with outdated references in libgnet-dev to glib include dirs.
A bug has been filed to solve this issue in gnet: https:/ /bugs.launchpad .net/ubuntu/ +source/ gnet/+bug/ 814374
Besides that, there are some problems in this package regarding indirect linking issues that I'm looking into.
Thanks,
Sebastian.