whilst trying to emerge kdelibs I get the following output: Error: dependent 'c:\Program\' does not exist. Reproducible: Always Steps to Reproduce: 0. fresh %KDEROOT% with only etc/kdesettings.bat and a newly cloned emerge (master branch) 1. emerge kdelibs Actual Results: Qt is now configured for building. Just run mingw32-make. To reconfigure, run mingw32-make confclean and configure. entering: c:\kderoot\build\libs\qt-all\work\mingw4-RelWithDebInfo-4.8.5 jom 1.0.13 - empower your cores cd src\tools\bootstrap\ && c:\kderoot\dev-utils\bin\jom.exe -f Makefile c:\kderoot\dev-utils\bin\jom.exe -f Makefile.Release Error: dependent 'c:\Program\' does not exist. jom: C:\KDERoot\build\libs\qt-all\work\mingw4-RelWithDebInfo-4.8.5\src\tools\bootstrap\Makefile [release] Error 2 jom: C:\kderoot\build\libs\qt-all\work\mingw4-RelWithDebInfo-4.8.5\Makefile [sub-tools-bootstrap-make_default-ordered] Error 2 emerge fatal error: while running make cmd: c:\kderoot\dev-utils\bin\jom.exe emerge fatal error: running python c:\kderoot\emerge\portage\libs\qt\qt-all.py compile emerge debug: Task: Emerge stopped after: 0:47:19.903000 Expected Results: kdelibs should compile to completion using emerge from the master branch using python 3.2 using mingw (installed during the emerge process) Looking at: C:\KDERoot\build\libs\qt-all\work\mingw4-RelWithDebInfo-4.8.5\src\tools\bootstrap\Makefile line 220 you can see: c:/Program\ Files\ (x86)/Microsoft\ Visual\ Studio/VC98/include/stddef.h It would appear that jom is not honouring the escapes for the spaces. It also makes me wonder why the VS includes are being looked for seeing as I've specified that mingw be used to do the compiling. I tested the jom theory by encapsulating the above path in "" jom then complained: Error: dependent 'c:\Program\ Files\ (x86)\Microsoft\ Visual\ Studio\VC98\include\stddef.h' does not exist. removing the escapes from the encapsulated path caused jom to revert to the original compilation error
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Please retry with a current craft, see docs here: https://community.kde.org/Craft
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!