Bug 280187

Summary: Wrong zlib-mingw4 path in python file
Product: [Unmaintained] kde-windows Reporter: benu.e
Component: buildsystemAssignee: KDE-Windows <windows-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description benu.e 2011-08-16 13:24:02 UTC 
Version:           unspecified (using Devel) 
OS:                MS Windows

The path for zlib at sourceforge has changed from 
http://sourceforge.net/projects/kde-windows/files/zlib/1.2.5-1/zlib-mingw4-1.2.5-1-bin.tar.bz2
to
http://sourceforge.net/projects/kde-windows/files/zlib/1.2.5-1/zlib-x86-mingw4-1.2.5-1-bin.tar.bz2
This should be changed in the python script.At the moment 'emerge qt' results in a 404 error.
This is quite the same bug as:
https://bugs.kde.org/show_bug.cgi?id=280182
I think all the paths in the buildsystem should be compared to the sourceforge paths and be corrected if necessary. I will report further bugs I get.  

Reproducible: Always

Steps to Reproduce:
Create a new kde root folder and add your kde-settings.
Do emerge qt

Actual Results:  
404 Error zlib file can not be found.

Expected Results:  
Normal zlib download
Comment 1 Patrick Spendrin 2012-02-22 22:29:25 UTC 
hm, the problem is different: these are different compilers: mingw4 means the gcc 4 version of the mingw.org compiler, x86-mingw4 is the gcc 4 version (32bit) of the mingw-w64 project. Those shouldn't be mixed, thats why their names are different. We switched this compiler a while ago already, so basically the mingw.org compiler shouldn't be used from our side anymore. Please either use the mingw-w64 compiler (default if you start a new emerge build with mingw4 as compiler in kdesettings.bat) or add 'set EMERGE_SOURCEONLY=True' if you want to still use the mingw4 from mingw.org.
Comment 2 Patrick Spendrin 2012-02-22 22:31:08 UTC 
*** Bug 280182 has been marked as a duplicate of this bug. ***