Package: bookmarkbridge
Version: 0.76-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080419 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now
the default on most architectures (even if it's not the case on i386 yet).
Feel free to downgrade this bug to 'important' if your package is only built
on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).

Relevant part:
> make[1]: Entering directory `/build/user/bookmarkbridge-0.76'
> make[1]: *** No rule to make target `distclean'.  Stop.
> make[1]: Leaving directory `/build/user/bookmarkbridge-0.76'
> make: [clean] Error 2 (ignored)
> dh_clean 
>  dpkg-source -b bookmarkbridge-0.76
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building bookmarkbridge using existing 
> bookmarkbridge_0.76.orig.tar.gz
> dpkg-source: info: building bookmarkbridge in bookmarkbridge_0.76-2.diff.gz
> dpkg-source: warning: executable mode 0755 of 
> 'debian/patches/01_dlghelp.dpatch' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 
> 'debian/patches/02_image_path.dpatch' will not be represented in diff
> dpkg-source: info: building bookmarkbridge in bookmarkbridge_0.76-2.dsc
>  debian/rules build
> test -d debian/patched || install -d debian/patched
> dpatch  apply-all  
> applying patch 01_dlghelp to ./ ... ok.
> applying patch 02_image_path to ./ ... ok.
> dpatch  cat-all  >>patch-stampT
> mv -f patch-stampT patch-stamp
> dh_testdir
> # Add here commands to configure the package.
> CFLAGS="-Wall -g -O2" LDFLAGS="-Wl,--as-needed" ./configure 
> --host=i486-linux-gnu \
> --build=i486-linux-gnu \
> --prefix=/usr \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info \
> --datadir=\${prefix}/share/doc \
> QT_CFLAGS="-DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui" \
> --disable-rpath
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for i486-linux-gnu-g++... i486-linux-gnu-g++
> checking for C++ compiler default output file name... a.out
> checking whether the C++ compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C++ compiler... yes
> checking whether i486-linux-gnu-g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of i486-linux-gnu-g++... gcc3
> checking for i486-linux-gnu-pkg-config... no
> checking for pkg-config... no
> checking for QT... configure: error: The pkg-config script could not be found 
> or is too old.  Make sure it
> is in your PATH or set the PKG_CONFIG environment variable to the full
> path to pkg-config.
> 
> Alternatively, you may set the environment variables QT_CFLAGS
> and QT_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> 
> To get pkg-config, see <http://www.freedesktop.org/software/pkgconfig>.
> See `config.log' for more details.
> make: *** [config.status] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/04/19

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to