Emerge errors

Patrick Spendrin ps_ml at gmx.de
Mon Nov 22 11:40:59 CET 2010

Am 22.11.2010 07:50, schrieb Gert Kello:
> Also the OpenSSL has incorrect version "1.0.0", but should be "1.0.0a"

I'd like to update openssl to 1.0.0b, that will need another 2 hours
from now. 1.0.0/1.0.0a was a bit messed up.

> Gert
>> I have found couple of errors in current emerge:
>> 1. emrge --target=4.5.0 mingw4 fails to unpack, the 7zip is not
>> installed automatically

Fixed in r1199667.

>> 2. seems like dbus version number/file name is wrong in emerge:
>> -2010-11-22 08:23:15--
>> http://downloads.sourceforge.net/kde-windows/dbus-mingw4-1.4.0-bin.tar.bz2
>> Resolving downloads.sourceforge.net...
>> Connecting to downloads.sourceforge.net||:80... connected.
>> HTTP request sent, awaiting response... 404 Not Found
>> 2010-11-22 08:23:15 ERROR 404: Not Found.
>> emerge fatal error: command fetch failed
>> emerge fatal error: running python
>> e:\kde4\emerge\portage\win32libs-bin\dbus\dbus-1.4.0.py fetch

Fixed in r1199660.

Hm, I am not sure how important that is for you: we want to change our
main mingw compiler away from the mingw4 to the mingw-wXX compilers.
Which means that mingw-w32 is equivalent to mingw4, but needs less
patches in our source code. Since you cannot mix mingw-w32 and mingw4
though, you might want to change while beginning to set up your build.


More information about the Kde-windows mailing list