Compiling 1.0.0 for KDE 4.3.4 for Windows

[pshute]

I'm starting from scratch on a different computer so I can play with this without worrying about losing any data.  I'm trying to follow the instructions at http://www.digikam.org/drupal/node/402.  Can anyone please explain why this isn't working for me?

The first difference I see compared to the screen shots in those instruction is at the second step.  The screen shots show a choice of  MinGW or MSVC compilers.  But I get a choice of MinGW4, MinGW, or MSVC 32 bit.  The instructions say to choose MinGW, so that's what I did.  Is that correct?

At the 4th step (i.e. 4th row of screen shots) it says to select the gcc-minw compiler from the devel-tools, but the closest thing I see is just called gcc.  Is that correct?

Then it suggests I could include the pre-compiled digiKam from the KDE group, but it isn't there.  It says this is optional and doesn't, but this makes me worried now.

It says to download kdebase, kdeedu, kdelibs, kdepimlibs, and kdesdk from the KDE grouip.  None of these are there, so I can't even proceed by guessing.

Any suggestions, anyone?  Should I be using a different compiler now?  If I choose MinGW4 or MSVC 32 bit I can find kdebase-apps, kdebase-runtime and kde-workspace. Are they, or one one them, the equivalent of kdebase?  In either case, kdesk is still not available.

I'm out of my depth here, so I feel that trying to guess my way any further is not going to be successful.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Patrick Spendrin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Shute schrieb:
> I'm starting from scratch on a different computer so I can play with this without worrying about losing any data.  I'm trying to follow the instructions at http://www.digikam.org/drupal/node/402.  Can anyone please explain why this isn't working for me?
>
> The first difference I see compared to the screen shots in those instruction is at the second step.  The screen shots show a choice of  MinGW or MSVC compilers.  But I get a choice of MinGW4, MinGW, or MSVC 32 bit.  The instructions say to choose MinGW, so that's what I did.  Is that correct?
Well, I would recommend to use mingw4 instead if you want to use the
Open Source compiler
>
> At the 4th step (i.e. 4th row of screen shots) it says to select the gcc-minw compiler from the devel-tools, but the closest thing I see is just called gcc.  Is that correct?
You can use either this compiler, or simply use the latest compiler from
mingw.org
>
> Then it suggests I could include the pre-compiled digiKam from the KDE group, but it isn't there.  It says this is optional and doesn't, but this makes me worried now.
>
> It says to download kdebase, kdeedu, kdelibs, kdepimlibs, and kdesdk from the KDE grouip.  None of these are there, so I can't even proceed by guessing.
>
Yeah, this is because mingw (gcc 3.4.5) is to old and no new packages
are provided anymore. This will change if you switch to mingw4.
> Any suggestions, anyone?  Should I be using a different compiler now?  If I choose MinGW4 or MSVC 32 bit I can find kdebase-apps, kdebase-runtime and kde-workspace. Are they, or one one them, the equivalent of kdebase?  In either case, kdesk is still not available.
>
The package you are looking for is kdebase-runtime. The other two are of
no interest when compiling digikam.
The kdesdk package should be there, if not please note here which mirror
you are using.
> I'm out of my depth here, so I feel that trying to guess my way any further is not going to be successful.


regards,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (MingW32)

iEYEARECAAYFAktL4mIACgkQi49rfdk/G3aNpQCdGYtYDqGEfOyEmg5B4e1cLpSu
8PQAn1V6kpT+3CYahjy6L/cMUN+vjCWj
=XGvN
-----END PGP SIGNATURE-----
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

Patrick Spendrin wrote on Tuesday, 12 January 2010 1:46 PM:

>> I'm starting from scratch on a different computer so I can play with
>> this without worrying about losing any data.  I'm trying to follow
>> the instructions at http://www.digikam.org/drupal/node/402.  Can
>> anyone please explain why this isn't working for me?  
>>
>> The first difference I see compared to the screen shots in those
>> instruction is at the second step.  The screen shots show a choice
>> of  MinGW or MSVC compilers.  But I get a choice of MinGW4, MinGW,
>> or MSVC 32 bit.  The instructions say to choose MinGW, so that's
>> what I did.  Is that correct?    

> Well, I would recommend to use mingw4 instead if you want to use the
> Open Source compiler

If I want to?  Is there an alternative?  I assumed the code would probably only work ok with compilers it's been tested on.  Not that I have any other compiler I'd prefer to use.
 

>> At the 4th step (i.e. 4th row of screen shots) it says to select the
>> gcc-minw compiler from the devel-tools, but the closest thing I see
>> is just called gcc.  Is that correct?  
> You can use either this compiler, or simply use the latest compiler
> from mingw.org
>>
>> Then it suggests I could include the pre-compiled digiKam from the
>> KDE group, but it isn't there.  It says this is optional and
>> doesn't, but this makes me worried now.  
>>
>> It says to download kdebase, kdeedu, kdelibs, kdepimlibs, and kdesdk
>> from the KDE grouip.  None of these are there, so I can't even
>> proceed by guessing.  
>>
> Yeah, this is because mingw (gcc 3.4.5) is to old and no new packages
> are provided anymore. This will change if you switch to mingw4.

>> Any suggestions, anyone?  Should I be using a different compiler
>> now?  If I choose MinGW4 or MSVC 32 bit I can find kdebase-apps,
>> kdebase-runtime and kde-workspace. Are they, or one one them, the
>> equivalent of kdebase?  In either case, kdesk is still not
>> available.    
>>
> The package you are looking for is kdebase-runtime. The other two are
> of no interest when compiling digikam.

OK, I see that now in the screen shot.  The text is being descriptive rather than precise.

> The kdesdk package should be there, if not please note here which
> mirror you are using.

I'm using winkde.org.  It seems to have less stuff missing than others I've tried, so I've been using just that one.

I just tried installing using the exact version mentioned in the instructions (KDE 4.1.2), even using the same installer (0.9.3), in order to confirm that it can be done.  I found that some of the components still had different names (no -mingw on the end), but the versions of them matched the screen shots, so I was able to reach the installation stage fairly confidant I had selected the right things.

But then some of the chosen components were unavailable for download so I had to ignore them to proceed.  When I repeated the procedure to try to get these missing components, the installer no longer allowed me to select Developer mode, and was defaulting to MSVC compiler, so I had to give up again.  What should one do when that happens?
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andrew Goodbody]

Peter Shute wrote:
> I'm starting from scratch on a different computer so I can play with
> this without worrying about losing any data.  I'm trying to follow
> the instructions at http://www.digikam.org/drupal/node/402.  Can
> anyone please explain why this isn't working for me?

I am guessing that it is old and out of date.

I'm following the instructions here

http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge

I am using the msvc compiler and it is working so far for me. It is
compiling qt currently. I did have an issue that the version of openssl
that it fetched was not a gzip file although it ended in .gz but that
was quickly fixed simply by gzipping the file and restarting the 'emerge
digikam'.

Andrew
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Patrick Spendrin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Shute schrieb:

> Patrick Spendrin wrote on Tuesday, 12 January 2010 1:46 PM:
>
>>> I'm starting from scratch on a different computer so I can play with
>>> this without worrying about losing any data.  I'm trying to follow
>>> the instructions at http://www.digikam.org/drupal/node/402.  Can
>>> anyone please explain why this isn't working for me?  
>>>
>>> The first difference I see compared to the screen shots in those
>>> instruction is at the second step.  The screen shots show a choice
>>> of  MinGW or MSVC compilers.  But I get a choice of MinGW4, MinGW,
>>> or MSVC 32 bit.  The instructions say to choose MinGW, so that's
>>> what I did.  Is that correct?    
>
>> Well, I would recommend to use mingw4 instead if you want to use the
>> Open Source compiler
>
> If I want to?  Is there an alternative?  I assumed the code would probably only work ok with compilers it's been tested on.  Not that I have any other compiler I'd prefer to use.

Well, you can always use Microsofts Visual Studio 2008 Express Edition
which is the compiler we use for the msvc binaries.

>  
>>> At the 4th step (i.e. 4th row of screen shots) it says to select the
>>> gcc-minw compiler from the devel-tools, but the closest thing I see
>>> is just called gcc.  Is that correct?  
>> You can use either this compiler, or simply use the latest compiler
>> from mingw.org
>>> Then it suggests I could include the pre-compiled digiKam from the
>>> KDE group, but it isn't there.  It says this is optional and
>>> doesn't, but this makes me worried now.  
>>>
>>> It says to download kdebase, kdeedu, kdelibs, kdepimlibs, and kdesdk
>>> from the KDE grouip.  None of these are there, so I can't even
>>> proceed by guessing.  
>>>
>> Yeah, this is because mingw (gcc 3.4.5) is to old and no new packages
>> are provided anymore. This will change if you switch to mingw4.
>
>>> Any suggestions, anyone?  Should I be using a different compiler
>>> now?  If I choose MinGW4 or MSVC 32 bit I can find kdebase-apps,
>>> kdebase-runtime and kde-workspace. Are they, or one one them, the
>>> equivalent of kdebase?  In either case, kdesk is still not
>>> available.    
>>>
>> The package you are looking for is kdebase-runtime. The other two are
>> of no interest when compiling digikam.
>
> OK, I see that now in the screen shot.  The text is being descriptive rather than precise.
>
>> The kdesdk package should be there, if not please note here which
>> mirror you are using.
>
> I'm using winkde.org.  It seems to have less stuff missing than others I've tried, so I've been using just that one.

yes, that is the seed server.
>
> I just tried installing using the exact version mentioned in the instructions (KDE 4.1.2), even using the same installer (0.9.3), in order to confirm that it can be done.  I found that some of the components still had different names (no -mingw on the end), but the versions of them matched the screen shots, so I was able to reach the installation stage fairly confidant I had selected the right things.
This doesn't really make sense.
Even if you get a KDE installed & working which is that old (that is ~
1.5 years now) you wouldn't get current digikam code compiling against
it. This is also the main problem why there are no newer digikam
releases yet. in KDE 4.3.4.
>
> But then some of the chosen components were unavailable for download so I had to ignore them to proceed.  When I repeated the procedure to try to get these missing components, the installer no longer allowed me to select Developer mode, and was defaulting to MSVC compiler, so I had to give up again.  What should one do when that happens?
If you have chosen developer mode once on an install directory, you
shouldn't change that later on. The default to the msvc compiler is
probably a bug though.

regards,
Patrick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (MingW32)

iEUEARECAAYFAktMrXoACgkQi49rfdk/G3ajjgCWLJTDMHGP5a4KUTz0c0Pz90iJ
vgCfXwE692KvWYsHY7EGK2eRG77PjoM=
=8DGf
-----END PGP SIGNATURE-----
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

Patrick Spendrin wrote on Wednesday, 13 January 2010 4:12 AM:

>> I just tried installing using the exact version mentioned in the
>> instructions (KDE 4.1.2), even using the same installer (0.9.3), in
>> order to confirm that it can be done.  I found that some of the
>> components still had different names (no -mingw on the end), but the
>> versions of them matched the screen shots, so I was able to reach
>> the installation stage fairly confidant I had selected the right
>> things.      

> This doesn't really make sense.
> Even if you get a KDE installed & working which is that old (that is ~
> 1.5 years now) you wouldn't get current digikam code compiling
> against it. This is also the main problem why there are no newer
> digikam releases yet. in KDE 4.3.4.  

Thanks, I wondered about that, so I won't pursue this method.  I don't understand what you mean by "the main problem why there are no newer digikam releases yet in KDE 4.3.4".  Are even the experts unable to get it compiled?
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

Andrew Goodbody wrote on Tuesday, 12 January 2010 7:37 PM:

> Peter Shute wrote:
>> I'm starting from scratch on a different computer so I can play with
>> this without worrying about losing any data.  I'm trying to follow
>> the instructions at http://www.digikam.org/drupal/node/402.  Can
>> anyone please explain why this isn't working for me?
>
> I am guessing that it is old and out of date.
>
> I'm following the instructions here
>
> http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge
>
> I am using the msvc compiler and it is working so far for me. It is
> compiling qt currently. I did have an issue that the version of
> openssl that it fetched was not a gzip file although it ended in .gz
> but that was quickly fixed simply by gzipping the file and restarting
> the 'emerge digikam'.    

This isn't for the faint hearted, is it?  I had to make a hole in the firewall for SVN, and then for git, which I've never heard of.  I came to the conclusion that the openssl file you mentioned has been fixed, it looked ok to me.  I assume it's C:\kderoot\download\openssl-0.9.8k.tar.gz?

But now I have what I assume are compilation arrors, and I'm not sure what to do.  Here are some sample compilation errors, there are hundreds of similar ones:
release/moc.o:moc.cpp:(.text+0x14b): undefined reference to `QByteArray::shared_null'
release/moc.o:moc.cpp:(.text+0x150): undefined reference to `QByteArray::shared_null'
release/moc.o:moc.cpp:(.text+0x156): undefined reference to `QByteArray::shared_null'

All I'm doing is typing "emerge digikam" and letting it do its thing.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andrew Goodbody]

Peter Shute wrote:
> This isn't for the faint hearted, is it?  I had to make a hole in the
> firewall for SVN, and then for git, which I've never heard of.  I
> came to the conclusion that the openssl file you mentioned has been
> fixed, it looked ok to me.  I assume it's
> C:\kderoot\download\openssl-0.9.8k.tar.gz?

git is the version control system currently used for the Linux kernel
and also in this case qt.
That was indeed the openssl file I mentioned, glad it's fixed.

> But now I have what I assume are compilation arrors, and I'm not sure
> what to do.  Here are some sample compilation errors, there are
> hundreds of similar ones: release/moc.o:moc.cpp:(.text+0x14b):
> undefined reference to `QByteArray::shared_null'
> release/moc.o:moc.cpp:(.text+0x150): undefined reference to
> `QByteArray::shared_null' release/moc.o:moc.cpp:(.text+0x156):
> undefined reference to `QByteArray::shared_null'
>
> All I'm doing is typing "emerge digikam" and letting it do its thing.

Which compiler are you using? I gave up on msvc. I was getting link
errors in strigi that seemed to come from differing interpretations of
wchar_t to that used in clucene. I am now using mingw4 and it is in the
middle of compiling webkit in qt. It seems to have successfully compiled
moc.cpp as there is a matching object file for it.

I set my path empty before calling kdeenv.bat just to avoid any
possibility of rogue tools in the path.

Andrew

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

Andrew Goodbody wrote on Thursday, 14 January 2010 7:44 PM:

> Peter Shute wrote:
>> But now I have what I assume are compilation arrors, and I'm not sure
>> what to do.  Here are some sample compilation errors, there are
>> hundreds of similar ones:
>> release/moc.o:moc.cpp:(.text+0x14b): undefined reference to `QByteArray::shared_null'
>> release/moc.o:moc.cpp:(.text+0x150): undefined reference to `QByteArray::shared_null'
>> release/moc.o:moc.cpp:(.text+0x156): undefined reference to `QByteArray::shared_null'
>>
>> All I'm doing is typing "emerge digikam" and letting it do its thing.
>
> Which compiler are you using? I gave up on msvc. I was getting link
> errors in strigi that seemed to come from differing interpretations
> of wchar_t to that used in clucene. I am now using mingw4 and it is
> in the middle of compiling webkit in qt. It seems to have
> successfully compiled moc.cpp as there is a matching object file for
> it.    

I'm using mingw4.
 
> I set my path empty before calling kdeenv.bat just to avoid any
> possibility of rogue tools in the path.

I just tried that, with the same result.  I'm not sure what to try next.
The files that are giving arrors are:
moc.cpp
preprocessor.cpp
generator.cpp
parser.cpp
main.cpp
I don't know what these are, but they sound important.

Did your compilation finish successfully?  If so, how long did it take?

Just fooling around trying things, I ran "emerge digikam-support".  It fails because it can't find http://saroengels.net/kde-windows/gnuwin32/digikam-support-0.2.0.tar.bz2.  It appears that in saroengels.net/kde-windows the directory gnuwin32 doesn't exist.  I don't know if this is related to the compilation problem.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andrew Goodbody]

Peter Shute wrote:

>> I set my path empty before calling kdeenv.bat just to avoid any
>> possibility of rogue tools in the path.
>
> I just tried that, with the same result.  I'm not sure what to try next.
> The files that are giving arrors are:
> moc.cpp
> preprocessor.cpp
> generator.cpp
> parser.cpp
> main.cpp
> I don't know what these are, but they sound important.

Can you paste into an email to the list at least part of your build
output, starting before the first compilation error and just a bit
after? I can only guess that you had a partial download leaving you with
an incomplete tree. There should be some clue in the page or so before
the first compilation error.

> Did your compilation finish successfully?  If so, how long did it take?

Yes it did finish successfully, although I have not tried it yet. I
don't know how long it took. I kept leaving it overnight or while I was
at work and came back to firewall popups and one time I had a bogus
failure complaining about a file that was in use (it wasn't). It
certainly took several hours, possibly double figures but my machine is
not particularly quick. I also had one failure, in webkit, due to my
%KDEROOT% being too long.

I would try:-

  emerge --unmerge qt

Then delete %KDEROOT%\download\svn-src\qt and try again. That should
fetch qt from scratch and give you a completely fresh start.

> Just fooling around trying things, I ran "emerge digikam-support".  It fails because it can't find http://saroengels.net/kde-windows/gnuwin32/digikam-support-0.2.0.tar.bz2.  It appears that in saroengels.net/kde-windows the directory gnuwin32 doesn't exist.  I don't know if this is related to the compilation problem.

That fails for me as well so cannot be related.

BTW the build also failed for me when I had the download directory
outside of %KDEROOT% as some Makefiles ended up with some incorrect
relative paths in them instead of absolute paths.

Andrew
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

I've used the same paths as on the instruction page, so at least I won't have that problem.



How do I capture all the output?



Emerge digikam > out.txt

doesn't get it all, and

Emerge digikam > out.txt 2>&1

gave an strange error. Sorry I can't remember what it was, maybe something about a file being open.



I ran it at work, so I'll have to set it all up here at home and try again if I want to do anything more with it before Wednesday.





--------------------------

Sent using BlackBerry



----- Original Message -----

From: Andrew Goodbody <[hidden email]>

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Sent: Sat Jan 16 03:08:57 2010
Subject: Re: [Digikam-users] Compiling digiKam with emerge - was Compiling 1.0.0 for KDE 4.3.4 for Windows



Peter Shute wrote:

>> I set my path empty before calling kdeenv.bat just to avoid any

>> possibility of rogue tools in the path.

>

> I just tried that, with the same result.  I'm not sure what to try next.

> The files that are giving arrors are:

> moc.cpp

> preprocessor.cpp

> generator.cpp

> parser.cpp

> main.cpp

> I don't know what these are, but they sound important.



Can you paste into an email to the list at least part of your build

output, starting before the first compilation error and just a bit

after? I can only guess that you had a partial download leaving you with

an incomplete tree. There should be some clue in the page or so before

the first compilation error.



> Did your compilation finish successfully?  If so, how long did it take?



Yes it did finish successfully, although I have not tried it yet. I

don't know how long it took. I kept leaving it overnight or while I was

at work and came back to firewall popups and one time I had a bogus

failure complaining about a file that was in use (it wasn't). It

certainly took several hours, possibly double figures but my machine is

not particularly quick. I also had one failure, in webkit, due to my

%KDEROOT% being too long.



I would try:-



  emerge --unmerge qt



Then delete %KDEROOT%\download\svn-src\qt and try again. That should

fetch qt from scratch and give you a completely fresh start.



> Just fooling around trying things, I ran "emerge digikam-support".  It fails because it can't find http://saroengels.net/kde-windows/gnuwin32/digikam-support-0.2.0.tar.bz2.  It appears that in saroengels.net/kde-windows the directory gnuwin32 doesn't exist.  I don't know if this is related to the compilation problem.



That fails for me as well so cannot be related.



BTW the build also failed for me when I had the download directory

outside of %KDEROOT% as some Makefiles ended up with some incorrect

relative paths in them instead of absolute paths.



Andrew

_______________________________________________

Digikam-users mailing list

[hidden email]

https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andrew Goodbody]

Peter Shute wrote:
> How do I capture all the output?

I don't know. What I would do would be to set the buffer history of the
Command Prompt window I was using to something huge, say 9999, and then
do the build. You can then select and copy the relevant section of
output to a text file. I'm assuming the build stops soon after the
compilation errors.

Andrew

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

I've set it all up at home now, so no problems with firewalls, and this time I cleared the path before starting , as you suggested.  So far it has been running for about 2.5 hours, and it's currently downloading git://gitorious.org/+kde-developers/qt/kde-qt.git.

This seems like a pretty big file (550MB) and the link to that server seems pretty slow - I calculate it will take another 3 hours to download.  I don't remember it taking anything like that long at work, although I left it running while I did other things, so I may have just forgotten about it.

Now I just have to keep the family away from it till it's done.  I hope git can resume downloads.

________________________________________
From: Andrew Goodbody [[hidden email]]
Sent: Saturday, 16 January 2010 7:15 AM
To: digiKam - Home Manage your photographs as a professional with the power of open source
Subject: Re: [Digikam-users] Compiling digiKam with emerge - was Compiling 1.0.0 for KDE 4.3.4 for Windows

Peter Shute wrote:
> How do I capture all the output?

I don't know. What I would do would be to set the buffer history of the
Command Prompt window I was using to something huge, say 9999, and then
do the build. You can then select and copy the relevant section of
output to a text file. I'm assuming the build stops soon after the
compilation errors.

Andrew

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

The long download mentioned below ran for just another 30 minutes, I think the download rate the program displayed was incorrect.  The whole process then ran for a few more hours, about 5 hours in total, then crashed.  Below are the last few lines that were displayed.  It looks like the same problem mentioned here:
http://bugreports.qt.nokia.com/browse/QTBUG-6017

I suppose I need to decipher the the solution mentioned there in order to continue.

g++ -c -include tmp\obj\release_shared\lib_pch.h -O2 -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_STATICPLUGIN -DQDESIGNER_COMPONENTS_LIBRARY -DQT_DLL -DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I"..\..\..\..\..\include\QtDesigner" -I"..\..\..\..\..\include\QtCore" -I"..\..\..\..\..\include\QtGui" -I"..\..\..\..\..\include\QtXml" -I"..\..\..\..\..\include\QtScript" -I"..\..\..\..\..\include" -I"c:\kderoot\build\win32libs-bin\dbus-1.2.4\image\include" -I"c:\kderoot\build\win32libs-bin\openssl-0.9.8k\image\include" -I"c:\kderoot\build\testing\mysql-server-5.1.36\image\include" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\lib" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\lib\components" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\lib\sdk" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\lib\extension" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\lib\uilib" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\lib\shared" -I"c:\kderoot\build\libs\qt-4.6.0.20100109\work\mingw4-RelWithDebInfo-4.6\tools\designer\src\components\propertyeditor" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\propertyeditor" -I"c:\kderoot\download\svn-src\qt\tools\shared\qtpropertybrowser" -I"c:\kderoot\download\svn-src\qt\tools\shared\qtgradienteditor" -I"c:\kderoot\download\svn-src\qt\tools\shared\findwidget" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\objectinspector" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\signalsloteditor" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\formeditor" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\widgetbox" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\buddyeditor" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\taskmenu" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\propertyeditor" -I"c:\kderoot\build\libs\qt-4.6.0.20100109\work\mingw4-RelWithDebInfo-4.6\tools\designer\src\components\taskmenu" -I"c:\kderoot\download\svn-src\qt\tools\shared\qtpropertybrowser" -I"c:\kderoot\download\svn-src\qt\tools\designer\src\components\tabordereditor" -I"..\..\..\..\..\include\ActiveQt" -I"tmp\moc\release_shared" -I"." -I"None" -I"c:\kderoot\build\win32libs-bin\dbus-1.2.4\image\include" -I"c:\kderoot\build\win32libs-bin\openssl-0.9.8k\image\include" -I"c:\kderoot\build\testing\mysql-server-5.1.36\image\include" -I"." -I"c:\kderoot\download\svn-src\qt\mkspecs\win32-g++" -o tmp\obj\release_shared\qtvariantproperty.o c:\kderoot\download\svn-src\qt\tools\shared\qtpropertybrowser\qtvariantproperty.cpp
c:\kderoot\download\svn-src\qt\tools\shared\qtpropertybrowser\qtvariantproperty.cpp: In constructor 'QtVariantEditorFactory::QtVariantEditorFactory(QObject*)':
c:\kderoot\download\svn-src\qt\tools\shared\qtpropertybrowser\qtvariantproperty.cpp:1927: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
mingw32-make[12]: *** [tmp/obj/release_shared/qtvariantproperty.o] Error 1
mingw32-make[12]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src/components/lib'
mingw32-make[11]: *** [release] Error 2
mingw32-make[11]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src/components/lib'
mingw32-make[10]: *** [all] Error 2
mingw32-make[10]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src/components/lib'
mingw32-make[9]: *** [sub-lib-make_default-ordered] Error 2
mingw32-make[9]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src/components'
mingw32-make[8]: *** [all] Error 2
mingw32-make[8]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src/components'
mingw32-make[7]: *** [sub-components-make_default-ordered] Error 2
mingw32-make[7]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src'
mingw32-make[6]: *** [all] Error 2
mingw32-make[6]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer/src'
mingw32-make[5]: *** [sub-src-make_default] Error 2
mingw32-make[5]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer'
mingw32-make[4]: *** [all] Error 2
mingw32-make[4]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools/designer'
mingw32-make[3]: *** [sub-designer-make_default-ordered] Error 2
mingw32-make[3]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools'
mingw32-make[2]: *** [all] Error 2
mingw32-make[2]: Leaving directory `C:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6/tools'
mingw32-make[1]: *** [sub-tools-make_default-ordered] Error 2
mingw32-make[1]: Leaving directory `c:/kderoot/build/libs/qt-4.6.0.20100109/work/mingw4-RelWithDebInfo-4.6'
mingw32-make: *** [all] Error 2
emerge fatal error: while running make cmd: mingw32-make
emerge fatal error: running python c:\kderoot\emerge\portage\libs\qt\qt-4.6.0.20100109.py compile
emerge error: fatal error: package libs/qt-4.6.0.20100109 all failed
02:21 PM

________________________________________
From: Peter Shute [[hidden email]]
Sent: Saturday, 16 January 2010 10:05 AM
To: digiKam - Home Manage your photographs as a professional with the power of open source
Subject: Re: [Digikam-users] Compiling digiKam with emerge - was Compiling 1.0.0 for KDE 4.3.4 for Windows

I've set it all up at home now, so no problems with firewalls, and this time I cleared the path before starting , as you suggested.  So far it has been running for about 2.5 hours, and it's currently downloading git://gitorious.org/+kde-developers/qt/kde-qt.git.

This seems like a pretty big file (550MB) and the link to that server seems pretty slow - I calculate it will take another 3 hours to download.  I don't remember it taking anything like that long at work, although I left it running while I did other things, so I may have just forgotten about it.

Now I just have to keep the family away from it till it's done.  I hope git can resume downloads.

________________________________________
From: Andrew Goodbody [[hidden email]]
Sent: Saturday, 16 January 2010 7:15 AM
To: digiKam - Home Manage your photographs as a professional with the power of open source
Subject: Re: [Digikam-users] Compiling digiKam with emerge - was Compiling 1.0.0 for KDE 4.3.4 for Windows

Peter Shute wrote:
> How do I capture all the output?

I don't know. What I would do would be to set the buffer history of the
Command Prompt window I was using to something huge, say 9999, and then
do the build. You can then select and copy the relevant section of
output to a text file. I'm assuming the build stops soon after the
compilation errors.

Andrew

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users