On 2009-04-18 09:36:37 (-0700), John Stamp <jst...@users.sourceforge.net> wrote:
> There are only a few minor changes between -1 and -2, and mips 
> successfully completed a bin-NMU of -1+b2 on March 11.
> 
> Here's the relevant snippet from the build of -1+b2:
> 
> > /usr/bin/uic-qt4 confirmdialog.ui -o ../../build/ui_confirmdialog.h
> > g++ -c -pipe -g -O2 -g -Wall -O2 -w -D_REENTRANT -fPIC -DNBREAKPAD
> > -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB
> > -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I.
> > -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore
> > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtNetwork
> > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui -I/usr/include/qt4
> > -I. -I../libUnicorn -I../../src -I../../build
> > -I../../build/Moose/release -I../../build
> > -o ../../build/Moose/release/confirmdialog.o confirmdialog.cpp
> 
> And the same section just before the errors that you cited for -2:
> 
> > /usr/bin/uic-qt4 confirmdialog.ui -o ../../../../ui_confirmdialog.h
> > g++ -c -pipe -g -O2 -g -Wall -O2 -w -D_REENTRANT -fPIC -DNBREAKPAD
> > -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB
> > -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I.
> > -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore
> > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtNetwork
> > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui -I/usr/include/qt4
> > -I/src/libMoose -I/src/libUnicorn -I/src -I/build
> > -I../../../../Moose/release -I/build
> > -o ../../../../Moose/release/confirmdialog.o confirmdialog.cpp
> 
> As you can see, a number of include and destination paths are broken.  
> e.g.:
>   -I/src/libMoose -I/src/libUnicorn -I/src -I/build
> 
> I suspect the problem is related to lastfm's definitions.pro.inc, where 
> it defines:
> 
>     ROOT_DIR = $$system( pwd )
> 
> and proceeds from there:
> 
>     BIN_DIR = $$ROOT_DIR/bin
>     DESTDIR = $$BIN_DIR
>     [...]
>     INCLUDEPATH += $$ROOT_DIR/src/libMoose $$ROOT_DIR/src/libUnicorn
>     [...]
> 
> Any idea why this now a problem?

No. We did find out there is an incompatibility between glibc and the kernel
installed on the mips buildds. I'm not sure this is related, but I want to wait
to look into this until we fixed this issue.

Cheers,

Peter.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to