Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 56539 - Kdevelop will on run "configure" when the project is in a directory with spaces in the path
Summary: Kdevelop will on run "configure" when the project is in a directory with spac...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo KDE team
Depends on:
Reported: 2004-07-09 07:17 UTC by Heath H Holcomb
Modified: 2004-07-09 07:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Heath H Holcomb 2004-07-09 07:17:22 UTC
If you have a kdevelop project in a directory that has spaces in it's path then it fails to run configure.  If you drop to a shell and type in "./configure" it works fine.  You have to move the project to a directory that does not contain any spaces and it works fine.

Reproducible: Always
Steps to Reproduce:
1. create kdevelop project (or move an existing one)
2. place the project in /home/user/KDE Developement (not the space in between "KDE and "Developement")
3. in KDevelop "Build"->"Run Configure"

Actual Results:  
Kdevelop gives you errors, such as : 
*cd "/home/hholcomb/Cerebro Data/Development/k3ddesktop" && 
"/home/hholcomb/Cerebro Data/Development/k3ddesktop/configure"  
*/home/hholcomb/Cerebro Data/Development/k3ddesktop/configure: line 877: 
test: /home/hholcomb/Cerebro: binary operator expected  
*/home/hholcomb/Cerebro Data/Development/k3ddesktop/configure: line 883: 
test: /home/hholcomb/Cerebro: binary operator expected  
*configure: error: sources are in /home/hholcomb/Cerebro 
Data/Development/k3ddesktop, but `cd /home/hholcomb/Cerebro 
Data/Development/k3ddesktop' does not work 

Expected Results:  
it configure properly
Comment 1 Heath H Holcomb 2004-07-09 07:21:26 UTC
See this bug report :

Comment 2 Caleb Tennis (RETIRED) gentoo-dev 2004-07-09 07:58:32 UTC
So it's an upstream bug that will have to be fixed by the KDevelop developers.