|

»

Fresh buildsystem fails while server doesn't

View: New views

4 Messages — Rating Filter: Alert me

	Fresh buildsystem fails while server doesn't by Bugzilla from casper.vandonderen@gmail.com :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I deleted my KDE trunk yesterday to start all anew against Qt 4.6 but it fails already at strigi. My kdesettings.bat is the same as before. I get the following cmake output (more text is below): c:\KDE4>emerge strigi emerge.bat executed 06:23 emerge debug: buildAction: all emerge debug: packageName: strigi emerge debug: buildType: RelWithDebInfo emerge debug: buildTests: None ________________________________________________________________________________ Unable to use key file "c:UsersCasperSSH-key.ppk" (unable to open file) entering: c:\KDE4\build\kdesupport\strigi-0.6.5.20090413\work\msvc2008-RelWithDebInfo-svnHEAD cleaning c:\KDE4\build\kdesupport\strigi-0.6.5.20090413\work\msvc2008-RelWithDebInfo-svnHEAD entering: c:\KDE4\build\kdesupport\strigi-0.6.5.20090413\work\msvc2008-RelWithDebInfo-svnHEAD emerge debug: cmake -G "NMake Makefiles" -DCMAKE_INSTALL_PREFIX="c:/KDE4" -DCMAKE_INCLUDE_PATH="c:/KDE4/include" -DCMAKE_LIBRARY_PATH= "c:/KDE4/lib" -DCMAKE_BUILD_TYPE=RelWithDebInfo "c:\KDE4\svn\trunk/kdesupport/strigi" -- The C compiler identification is MSVC -- The CXX compiler identification is MSVC -- Check for CL compiler version -- Check for CL compiler version - 1500 -- Check if this is a free VC compiler -- Check if this is a free VC compiler - no -- Check CL platform -- Check CL platform - 32 bit -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin/cl.exe -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin/cl.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin/cl.exe -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin/cl.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found ZLIB: C:/KDE4/lib/zlib.lib -- Found BZip2: C:/KDE4/lib/bzip2.lib -- Looking for BZ2_bzCompressInit in C:/KDE4/lib/bzip2.lib -- Looking for BZ2_bzCompressInit in C:/KDE4/lib/bzip2.lib - found -- Looking for include files CMAKE_HAVE_PTHREAD_H -- Looking for include files CMAKE_HAVE_PTHREAD_H - not found. -- Found Threads: TRUE -- Performing Test ICONV_SECOND_ARGUMENT_IS_CONST -- Performing Test ICONV_SECOND_ARGUMENT_IS_CONST - Failed -- Found Iconv: C:/KDE4/lib/libiconv-2.lib Expat is disabled. No support for XML via Expat -- Found LibXml2: C:/KDE4/lib/libxml2.lib -- Found CLucene library: C:/KDE4/lib/clucene-core.lib -- Found CLucene include dir: C:/KDE4/include -- Found CLucene library dir: C:/KDE4/include -- Found CLucene: C:/KDE4/lib/clucene-core.lib CLucene is found. Support for CLucene backend is enabled HyperEstraier is disabled. No support for HyperEstraier backend SQLite is disabled. No support for SQLite backend -- Found Exiv2: C:/KDE4/lib/exiv2.lib Exiv2 is found. Support for indexing of EXIF/IPTC metadata is enabled -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - not found. -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found. -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found. -- Found Qt-Version 4.6.0 with qmake at C:/KDE4/bin/qmake.exe Qt4 is found. Support for Qt4 GUI client is enabled Log4cxx is disabled. No support for advanced logging -- Ensure you cppunit installed version is at least 1.12.0 CppUnit not found. Support for Strigi unit tests is disabled -- Looking for C++ include direct.h -- Looking for C++ include direct.h - found -- Looking for C++ include dirent.h -- Looking for C++ include dirent.h - not found -- Looking for C++ include dlfcn.h -- Looking for C++ include dlfcn.h - not found -- Looking for C++ include ndir.h -- Looking for C++ include ndir.h - not found -- Looking for C++ include stddef.h -- Looking for C++ include stddef.h - found -- Looking for C++ include sys/dir.h -- Looking for C++ include sys/dir.h - not found -- Looking for C++ include sys/ndir.h -- Looking for C++ include sys/ndir.h - not found -- Looking for C++ include windows.h -- Looking for C++ include windows.h - found -- Looking for C++ include socket.h -- Looking for C++ include socket.h - not found -- Looking for C++ include sys/socket.h -- Looking for C++ include sys/socket.h - not found -- Looking for C++ include sys/types.h -- Looking for C++ include sys/types.h - found -- Looking for C++ include unistd.h -- Looking for C++ include unistd.h - not found -- Looking for C++ include stdint.h -- Looking for C++ include stdint.h - not found -- Looking for C++ include regex.h -- Looking for C++ include regex.h - not found -- Looking for include files HAVE_STRINGS_H -- Looking for include files HAVE_STRINGS_H - not found. -- Looking for fchdir -- Looking for fchdir - not found -- Looking for gettimeofday -- Looking for gettimeofday - not found -- Looking for isblank -- Looking for isblank - not found -- Looking for mkstemp -- Looking for mkstemp - not found -- Looking for nanosleep -- Looking for nanosleep - not found -- Looking for setenv -- Looking for setenv - not found -- Looking for strcasecmp -- Looking for strcasecmp - not found -- Looking for strcasestr -- Looking for strcasestr - not found -- Looking for strlwr -- Looking for strlwr - found -- Looking for strncasecmp -- Looking for strncasecmp - not found -- Check for ANSI scope -- Check for ANSI scope - found -- Check size of int8_t -- Check size of int8_t - failed -- Check size of uint8_t -- Check size of uint8_t - failed -- Check size of int16_t -- Check size of int16_t - failed -- Check size of uint16_t -- Check size of uint16_t - failed -- Check size of int32_t -- Check size of int32_t - failed -- Check size of uint32_t -- Check size of uint32_t - failed -- Check size of int64_t -- Check size of int64_t - failed -- Check size of uint64_t -- Check size of uint64_t - failed -- Check size of char -- Check size of char - done -- Check size of short -- Check size of short - done -- Check size of int -- Check size of int - done -- Check size of long -- Check size of long - done -- Check size of long long -- Check size of long long - done -- Check size of size_t -- Check size of size_t - done -- Check size of ssize_t -- Check size of ssize_t - failed -- Check size of uint -- Check size of uint - failed -- Check size of intptr_t -- Check size of intptr_t - done -- Check size of socklen_t -- Check size of socklen_t - failed -- Looking for connect in socket -- Looking for connect in socket - not found -- C:/KDE4/lib - C:/KDE4 -- Configuring done -- Generating done -- Build files have been written to: C:/KDE4/build/kdesupport/strigi-0.6.5.20090413/work/msvc2008-RelWithDebInfo-svnHEAD entering: c:\KDE4\build\kdesupport\strigi-0.6.5.20090413\work\msvc2008-RelWithDebInfo-svnHEAD jom 0.6.8 - empower your cores C:\KDE4\dev-utils\bin\cmake.exe -HC:\KDE4\svn\trunk\kdesupport\strigi -BC:\KDE4\build\kdesupport\strigi-0.6.5.20090413\work\msvc2008-Re lWithDebInfo-svnHEAD --check-build-system CMakeFiles\Makefile.cmake 0 CMake Error: Parse error in cache file C:/KDE4/build/kdesupport/strigi-0.6.5.20090413/work/msvc2008-RelWithDebInfo-svnHEAD/CMakeCache.t xt. Offending entry: Error processing project file: C:/KDE4/build/kdesupport/strigi-0.6.5.20090413/work/msvc2008-RelWithDebInfo-svnHEAD /CMakeFiles/CMakeTmpQmake/tmp.pro CMake Error: Parse error in cache file C:/KDE4/build/kdesupport/strigi-0.6.5.20090413/work/msvc2008-RelWithDebInfo-svnHEAD/CMakeCache.t xt. Offending entry: Error processing project file: C:/KDE4/build/kdesupport/strigi-0.6.5.20090413/work/msvc2008-RelWithDebInfo-svnHEAD /CMakeFiles/CMakeTmpQmake/tmp.pro Expat is disabled. No support for XML via Expat -- Found CLucene library: C:/KDE4/lib/clucene-core.lib -- Found CLucene include dir: C:/KDE4/include -- Found CLucene library dir: C:/KDE4/include -- Found CLucene: C:/KDE4/lib/clucene-core.lib CLucene is found. Support for CLucene backend is enabled HyperEstraier is disabled. No support for HyperEstraier backend SQLite is disabled. No support for SQLite backend Exiv2 is found. Support for indexing of EXIF/IPTC metadata is enabled -- Found Qt-Version 4.6.0 with qmake at C:/KDE4/bin/qmake.exe -- Ensure you cppunit installed version is at least 1.12.0 Qt4 is found. Support for Qt4 GUI client is enabled Log4cxx is disabled. No support for advanced logging CppUnit not found. Support for Strigi unit tests is disabled -- C:/KDE4/lib - C:/KDE4 -- Configuring incomplete, errors occurred! command failed with exit code 1 emerge fatal error: while running make cmd: c:\KDE4\bin\jom.exe emerge fatal error: running python c:\KDE4\emerge\portage\kdesupport\strigi\strigi-0.6.5.20090413.py compile emerge error: fatal error: package kdesupport/strigi-0.6.5.20090413 all failed 06:25 c:\KDE4>C:\KDE4\bin\jom.exe jom 0.6.8 - empower your cores File Makefile doesn't exist. c:\KDE4> That CMakeTmpQmake folder does not even exist. Then if I run jom/nmake from the build folder it just starts till it encounters the following error: [ 77] Generating moc_filebrowser.cxx 'QMAKESPEC" has not been set, so configuration cannot be "deduced.' is not recognized as an internal or external command, operable program or batch file. command failed with exit code 1 command failed with exit code 2 [ 77] QProcess: Destroyed while process is still running. command failed with exit code 2 command failed with exit code 2 command failed with exit code 2 Any ideas why this is happening? Casper _______________________________________________ Kde-windows mailing list Kde-windows@... https://mail.kde.org/mailman/listinfo/kde-windows
	Re: Fresh buildsystem fails while server doesn't by Bugzilla from ps_ml@gmx.de :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Casper van Donderen schrieb: > I deleted my KDE trunk yesterday to start all anew against Qt 4.6 but > it fails already at strigi. > c:\KDE4>C:\KDE4\bin\jom.exe > jom 0.6.8 - empower your cores > > File Makefile doesn't exist. > > c:\KDE4> > > > That CMakeTmpQmake folder does not even exist. > > Then if I run jom/nmake from the build folder it just starts till it > encounters the following error: > > [ 77] Generating moc_filebrowser.cxx > 'QMAKESPEC" has not been set, so configuration cannot be "deduced.' is > not recognized as an internal or external command, > operable program or batch file. > command failed with exit code 1 > command failed with exit code 2 > [ 77] QProcess: Destroyed while process is still running. > command failed with exit code 2 > command failed with exit code 2 > command failed with exit code 2 > > > > Any ideas why this is happening? Please check if your Qt provides the mkspecs folder (look into %KDEROOT%\build\libs\qt-\image\mkspecs\win32-msvc2008). Somehow our Qt build fails from time to time to copy that one.... > > Casper > _______________________________________________ > Kde-windows mailing list > Kde-windows@... > https://mail.kde.org/mailman/listinfo/kde-windows > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkrmu/AACgkQi49rfdk/G3ZRjACcD2D493QSnEQyau8jg218xNBo FjoAn0kPlpfc/5r3NFKSHF1cu66+2Bmq =Rthp -----END PGP SIGNATURE----- _______________________________________________ Kde-windows mailing list Kde-windows@... https://mail.kde.org/mailman/listinfo/kde-windows
	Re: Fresh buildsystem fails while server doesn't by Bugzilla from casper.vandonderen@gmail.com :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Thanks, it was indeed not compiled... redoing it now :-). Casper On Tue, Oct 27, 2009 at 10:22 AM, Patrick Spendrin <ps_ml@...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Casper van Donderen schrieb: >> I deleted my KDE trunk yesterday to start all anew against Qt 4.6 but >> it fails already at strigi. > >> c:\KDE4>C:\KDE4\bin\jom.exe >> jom 0.6.8 - empower your cores >> >> File Makefile doesn't exist. >> >> c:\KDE4> >> >> >> That CMakeTmpQmake folder does not even exist. >> >> Then if I run jom/nmake from the build folder it just starts till it >> encounters the following error: >> >> [ 77] Generating moc_filebrowser.cxx >> 'QMAKESPEC" has not been set, so configuration cannot be "deduced.' is >> not recognized as an internal or external command, >> operable program or batch file. >> command failed with exit code 1 >> command failed with exit code 2 >> [ 77] QProcess: Destroyed while process is still running. >> command failed with exit code 2 >> command failed with exit code 2 >> command failed with exit code 2 >> >> >> >> Any ideas why this is happening? > Please check if your Qt provides the mkspecs folder (look into > %KDEROOT%\build\libs\qt-\image\mkspecs\win32-msvc2008). Somehow our Qt > build fails from time to time to copy that one.... >> >> Casper >> _______________________________________________ >> Kde-windows mailing list >> Kde-windows@... >> https://mail.kde.org/mailman/listinfo/kde-windows >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > > iEYEARECAAYFAkrmu/AACgkQi49rfdk/G3ZRjACcD2D493QSnEQyau8jg218xNBo > FjoAn0kPlpfc/5r3NFKSHF1cu66+2Bmq > =Rthp > -----END PGP SIGNATURE----- > _______________________________________________ > Kde-windows mailing list > Kde-windows@... > https://mail.kde.org/mailman/listinfo/kde-windows > _______________________________________________ Kde-windows mailing list Kde-windows@... https://mail.kde.org/mailman/listinfo/kde-windows
	Re: Fresh buildsystem fails while server doesn't by Ralf Habacker :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Patrick Spendrin schrieb: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Casper van Donderen schrieb: > >> I deleted my KDE trunk yesterday to start all anew against Qt 4.6 but >> it fails already at strigi. >> > > >> c:\KDE4>C:\KDE4\bin\jom.exe >> jom 0.6.8 - empower your cores >> >> File Makefile doesn't exist. >> >> c:\KDE4> >> >> >> That CMakeTmpQmake folder does not even exist. >> >> Then if I run jom/nmake from the build folder it just starts till it >> encounters the following error: >> >> [ 77] Generating moc_filebrowser.cxx >> 'QMAKESPEC" has not been set, so configuration cannot be "deduced.' is >> not recognized as an internal or external command, >> operable program or batch file. >> command failed with exit code 1 >> command failed with exit code 2 >> [ 77] QProcess: Destroyed while process is still running. >> command failed with exit code 2 >> command failed with exit code 2 >> command failed with exit code 2 >> >> >> >> Any ideas why this is happening? >> > Please check if your Qt provides the mkspecs folder (look into > %KDEROOT%\build\libs\qt-\image\mkspecs\win32-msvc2008). Somehow our Qt > build fails from time to time to copy that one.... > I recognized some fails when there is no mkspecs/default folder which should be copied from the recent compiler mkspecs. I added some code to the qt install step to create this by default. Regards Ralf _______________________________________________ Kde-windows mailing list Kde-windows@... https://mail.kde.org/mailman/listinfo/kde-windows