Bug 1376 - Space in directory name prevents build after compile
Summary: Space in directory name prevents build after compile
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Config Files (show other bugs)
Version: 3.0.4
Hardware: PPC Mac OS X
: P3 minor
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact:
Depends on:
Reported: 2004-05-22 22:41 UTC by Anders Kirchenbauer
Modified: 2006-04-08 22:49 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Anders Kirchenbauer 2004-05-22 22:41:37 UTC
Mac OS X has a solid UNIX background and as such mounts all HDD as well as CD and external drives 
under a directory called Volumes. For usability in the GUI many drive names have spaces in them. 
Instead of representing the space as "¥ " the space is represented as " " which is incorrect and causes 
the build to be unable to proceed. I know this to be the case on several normal Linux and *BSD 
distributions as well. This is minor because anyone who would be building should have enough 
knowledge to use a symbolic link to get around the issue anyway.
Comment 1 Tim Potter 2004-05-23 03:30:58 UTC
Can you post some output to illustrate the problem?
Comment 2 Anders Kirchenbauer 2004-05-23 07:03:35 UTC
configure: creating ./config.status
config.status: creating include/stamp-h
config.status: creating Makefile
config.status: creating script/findsmb
config.status: creating smbadduser
config.status: creating script/gen-8bit-gap.sh
config.status: creating include/config.h
Tirako:/Volumes/Tirako UFS/code/samba-3.0.4/source ack$ make
make: Circular /Volumes/Tirako <- /Volumes/Tirako dependency dropped.
make: *** No rule to make target `UFS/code/samba-3.0.4/source/configure.in', needed by `/Volumes/
Tirako'.  Stop.
Tirako:/Volumes/Tirako UFS/code/samba-3.0.4/source ack$ pwd
/Volumes/Tirako UFS/code/samba-3.0.4/source
Comment 3 Gerald (Jerry) Carter (dead mail address) 2006-04-08 22:49:18 UTC
Please retest against a current release and reopen if the issue still exists.