Hello,

I tried using emerge to build kde (and thus qt). This failed.

Code: Select all

C:\KDE>emerge qt
emerge.bat executed
12:32
emerge debug: buildAction: all
emerge debug: doPretend: False
emerge debug: packageName: qt
emerge debug: buildType: RelWithDebInfo
emerge debug: buildTests: None
emerge debug: verbose: 1
emerge debug: KDEROOT: c:\KDE

________________________________________________________________________________

['c:\\KDE\\emerge\\portage\\libs\\qt\\qt-4.5.2.20090727.py', 'fetch']
msys execute: c:\KDE\dev-utils\git\bin\sh.exe --login -c "cd /c/KDE/build/libs/q
t-4.5.2.20090727/work && git pull"
fatal: Not a git repository (or any of the parent directories): .git
emerge fatal error: msys execute failed. cmd: c:\KDE\dev-utils\git\bin\sh.exe --
login -c "cd /c/KDE/build/libs/qt-4.5.2.20090727/work && git pull"
emerge fatal error: running python c:\KDE\emerge\portage\libs\qt\qt-4.5.2.200907
27.py fetch
emerge error: fatal error: package libs/qt-4.5.2.20090727 all failed
12:32


As I understand it, emerge tries to get the sources for building. I tried doing this manually, by cloning git://gitorious.org/+kde-developers/qt/kde-qt.git /c/KDE/libs/qt-4.5.2.20090727/work.

After doing that, emerge correctly runs git but another problem arises: it tries to copy the whole work directory to work/mingw-patched (well, actually another directory, but I forgot the whole name). This won't stop, as it copies the mingw-patched itself too!

I hope someone can me with this matter.

EDIT:

I deleted my whole C:\KDE directory and tried again. This time I selected the build type to be Debug instead of RelWithDebInfo. Now it worked.

Maybe this is related to the build type, or it may be something else.

It is something else - i build in RelWithDebInfo mode myself and had this error 5-10 times in a row. Had to delete the dowloads/svn-src/qt directory so that Git couldbegin from scratch. I had to download everything in the night so that no other traffic (web-browser, bit-torrent client or anything else) interfere with Git. I succeded at that point (though, that might be not related too).

Maybe... In my case git works okay, but emerge doesn't detect that git hasn't got a repository yet (okay, that may be my fault, because I deleted it to retry).

My problem (so it seems, at least) was that emerge tried to "git pull" in the wrong directory.

I advise to build with Debug as build type. I had no problem whatsoever anymore when I switched to Debug. Release may work too, but I haven't tried yet.

PS: Please report if switching worked, if you try.
If it doesn't, I'll create a bugreport against emerge for the RelWithDebInfo build type.

As i already wrote, my current configuration is with RelWithDebInfo and it works fine. It just was rather hard to eventually make it pull the whole repo at once without hiccup. Since it works there're no actual bug. But the fact that it hiccups from time to time is certainly not good