qutecom version 2.2+dfsg1-2 failed to build on i386

Bug #756051 reported by Matthias Klose
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qutecom (Ubuntu)
Fix Released
High
Unassigned

Bug Description

qutecom version 2.2+dfsg1-2 failed to build on i386
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/+buildjob/2409020

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/+buildjob/2409020/+files/buildlog_ubuntu-natty-i386.qutecom_2.2%2Bdfsg1-2_FAILEDTOBUILD.txt.gz

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

Please set them or make sure they are set and tested correctly in the CMake files:
GLIBCONFIG_INCLUDE_DIR
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/libs/imwrapper
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/libs/sipwrapper/src/phapi
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/libs/imwrapper/src/purple
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/libs/imwrapper/src/multiim
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/wifo/phapi
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/qutecom/src/buildid
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/qutecom/src
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/qutecom/src/presentation/qt
   used as include directory in directory /build/buildd/qutecom-2.2+dfsg1/qutecom/src/presentation/qt/lang

-- Configuring incomplete, errors occurred!
make: *** [obj-i686-linux-gnu/CMakeCache.txt] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110408-1904
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/qutecom-2.2+dfsg1

Tags: ftbfs natty
Matthias Klose (doko)
Changed in qutecom (Ubuntu):
importance: Undecided → High
Revision history for this message
Ludovico Cavedon (cavedon) wrote :

Ok, same problem described here
#751940
preparing fix

Changed in qutecom (Ubuntu):
assignee: nobody → Ludovico Cavedon (cavedon)
status: New → In Progress
Revision history for this message
Ludovico Cavedon (cavedon) wrote :

Patch to fix the FTBFS.
Build cleanly in pbuilder.
Tested on a natty chroot.

Changed in qutecom (Ubuntu):
assignee: Ludovico Cavedon (cavedon) → nobody
status: In Progress → New
Revision history for this message
Scott Kitterman (kitterman) wrote :

No need to subscribe the release team for fixing bugs. I'm subscribed ubuntu-sponsors instead.

Revision history for this message
Jonathan Riddell (jr) wrote :

Compiling this in a natty pbuilder I get this error..

-- **
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
GLIBCONFIG_INCLUDE_DIR
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/libs/imwrapper
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/libs/sipwrapper/src/phapi
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/libs/imwrapper/src/purple
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/libs/imwrapper/src/multiim
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/wifo/phapi
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/qutecom/src/buildid
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/qutecom/src
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/qutecom/src/presentation/qt
   used as include directory in directory /tmp/buildd/qutecom-2.2+dfsg1/qutecom/src/presentation/qt/lang

-- Configuring incomplete, errors occurred!
make: *** [obj-x86_64-linux-gnu/CMakeCache.txt] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Revision history for this message
Ludovico Cavedon (cavedon) wrote : Re: [Bug 756051] Re: qutecom version 2.2+dfsg1-2 failed to build on i386

On 04/13/2011 05:24 AM, Jonathan Riddell wrote:
> Compiling this in a natty pbuilder I get this error..
>
> CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the CMake files:
> GLIBCONFIG_INCLUDE_DIR

Are you sure you applied my patch and you have an updated natty pbuilder
environment?

The error you are mentioning is exactly the error you get when do *not*
have the patch.

I tested it again and had no problem. Here is my log:

cavedon@huffman:/tmp$ dget
https://launchpad.net/ubuntu/+archive/primary/+files/qutecom_2.2%2Bdfsg1-2.dsc
[...]
cavedon@huffman:/tmp$ wget
https://bugs.launchpad.net/ubuntu/+source/qutecom/+bug/756051/+attachment/2025857/+files/qutecom_2.2%2Bdfsg1-2ubuntu1.debdiff
[...]
cavedon@huffman:/tmp$ cd qutecom-2.2+dfsg1/
cavedon@huffman:/tmp/qutecom-2.2+dfsg1$ patch -p1 <
../qutecom_2.2+dfsg1-2ubuntu1.debdiff
patching file debian/changelog
patching file debian/control
patching file debian/patches/find-glibconfig.patch
patching file debian/patches/new-videodev.patch
patching file debian/patches/series

cavedon@huffman:/tmp/qutecom-2.2+dfsg1$ dpkg-buildpackage -us -uc -S
[...]
cavedon@huffman:/tmp/qutecom-2.2+dfsg1$ cd ..
cavedon@huffman:/tmp$ sudo cowbuilder-dist natty i386 build
qutecom_2.2+dfsg1-2ubuntu1.dsc
[...]

and the package built successfully

Revision history for this message
Andreas Moog (ampelbein) wrote :

I am not quite sure that just adding

      /usr/lib/i386-linux-gnu/glib-2.0/include
      /usr/lib/x86_64-linux-gnu/glib-2.0/include

is the right way. What about armel and powerpc architectures? It would be better to use pkg-config to find correct paths in my opinion.

Revision history for this message
Ludovico Cavedon (cavedon) wrote :

On 04/13/2011 02:20 PM, Andreas Moog wrote:
> I am not quite sure that just adding
>
> /usr/lib/i386-linux-gnu/glib-2.0/include
> /usr/lib/x86_64-linux-gnu/glib-2.0/include
>
> is the right way. What about armel and powerpc architectures? It would
> be better to use pkg-config to find correct paths in my opinion.

I agree with you, but if the location of include files gets changed and
a FTBFS bugs gets fired 1 day before beta freeze, that's a fast fix to
get it building for the release architectures.

Moreover the right ways should be using the FindGLIB2.cmake from the
cmake package, which, in turn is supposed to use pkg-config.
But cmake is still working on that... LP #751940

Therefore, given the timing, this patch fixes the problem and does no
harm. I will do a proper longer-term fix starting from the debian package.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Uhm...

I tested this patch and in my case it does not FTBFS with the errors you are seeing there.

Revision history for this message
Andreas Moog (ampelbein) wrote :

I'm attaching a patch that allows this package to also build on armel and powerpc, by using pkg-config to find the correct paths to the librarys.

Revision history for this message
Jonathan Riddell (jr) wrote :

You are quite right, I was compiling the wrong version in my pbuilder. Uploaded with patch in comment #9

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qutecom - 2.2+dfsg1-2ubuntu1

---------------
qutecom (2.2+dfsg1-2ubuntu1) natty; urgency=low

  [ Ludovico Cavedon ]
  * Add find-glibconfig.patch to handle new location of glibconfig.h
    (LP: #756051).
  * Add new-videodev.patch (fix for moved videodev.h) and B-D on
    libc4l-dev.

  [ Andreas Moog ]
  * don't hardcode library paths, let pkg-config handle them
 -- Andreas Moog <email address hidden> Thu, 14 Apr 2011 00:16:28 +0200

Changed in qutecom (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.