Bug 59145

Summary:	Spaces in directory name for project cause configure/make failure
Product:	[Unmaintained] kdelibs	Reporter:	Benjamin Roe <ben>
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	andresbajotierra, grundleborg
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Benjamin Roe 2003-05-30 13:36:52 UTC

Version:           2.1.5 (using KDE KDE 3.1.2)
Installed from:    Gentoo Packages
Compiler:          gcc 3.2.1 
OS:          Linux

If I create any type of KDevelop project in a directory which has a space in its name, the configure and make scripts can't cope with it - for example:

Configuring and then making a project in /home/bdr/PhD Work/Interface gives the error:

/home/bdr/PhD: /home/bdr/PhD: No such file or directory 
configure: WARNING: `missing' script is too old or missing 

during configure and:

make: /home/bdr/PhD: No such file or directory 
make: *** No rule to make target `/home/bdr/PhD'. Stop. 
*** failed *** 

during Make. I think the filenames and directories need to be enclosed in quotes in the scripts.

Comment 1 Amilcar do Carmo Lucas 2003-05-30 13:58:32 UTC

This is a known bug. And it's also present in KDevelop 3.0 
This affects appwizard and autoproject (maybe other manangers as well)

Comment 2 Amilcar do Carmo Lucas 2004-01-21 14:31:08 UTC

KDevelop 3.0 quotes all paths, but the configure script fails anyway because it is wrongly invoked :(
I don't know how to fix this one.

i.e.
cd "/home/amilcar/my test/teftyvdghxf/debug" && CXXFLAGS="-O0 -g3" "/home/amilcar/my test/teftyvdghxf/configure" --enable-debug=full 
* /home/amilcar/my test/teftyvdghxf/configure: test: /home/amilcar/my: binary operator expected 
* /home/amilcar/my test/teftyvdghxf/configure: test: /home/amilcar/my: binary operator expected 
* configure: error: sources are in /home/amilcar/my test/teftyvdghxf

Comment 3 Sascha Cunz 2004-06-04 02:39:55 UTC

Amilcar, in case this still applies, we should handle that upwards to the guys taking care of the admin/ submodule and update the admin/-dir in our project templates. This is for sure some error in the m4 stuff or am_edit or such (Any of the tools used to produce configure)

Comment 4 Amilcar do Carmo Lucas 2004-07-18 23:16:54 UTC

Looks like the stuff in the admind directory should handle it.

Comment 5 George Goldberg 2008-02-18 04:31:35 UTC

Is this bug still present in a recent KDE version, such as 3.5.9 or 4.0.1?

Comment 6 Dario Andres 2009-06-01 16:19:38 UTC

Marking as NEEDSINFO

Comment 7 Christoph Feck 2013-07-24 20:07:02 UTC

automake based tools are unmaintained