Bug 3396

Summary:	Directory names can not contain spaces in its
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Alexandru Georgescu <alexandru.c.georgescu>
Component:	configuration	Assignee:	Scott Rifenbark <srifenbark>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	poky.bs.watcher, poky.watcher, richard.purdie, sgw, shiftee
Version:	1.4
Target Milestone:	1.4
Hardware:	x86
OS:	Multiple
URL:	http://git.yoctoproject.org/cgit.cgi/yocto-docs/commit/?id=1d102e91ba77391096749bd7df6c05b2b695b33f
Whiteboard:	15 Nov 2012 - Provided documentation. Need approval.
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Alexandru Georgescu 2012-11-06 14:40:33 UTC

GENERAL DESCRIPTION
An error appears when trying to source the poky environment on a mounted drive which contain spaces in its Filesystem Label name.

STEPS TO REPRODUCE
1. Mount an external drive containing spaces in the filesystem label name. (e.g. SSD DRIVE)
2. Go to that drive and get a poky clone
3. Try to source the environment

EXPECTED RESULTS
3. The environment is sourced

ACTUAL RESULTS:
yocto@yocto-o1:/media/SSD Volume/poky$ source oe-init-build-env 
bash: /media/SSD: No such file or directory
yocto@yocto-o1:/media/SSD Volume/poky$

Comment 1 Saul Wold 2012-11-07 09:29:25 UTC

There are lots of issues with spaces in directories, this is not something that the overall build system handles well at all.  I would suggest that this is a documentation issue (or a sanity check in the scripts).

Also, you need to provide more information about your build env in the future, while this bug had enough into, you do not say which branch or release version.

Comment 2 Alexandru Georgescu 2012-11-07 12:45:33 UTC

I have tested on a Ubuntu 12.10 machine using the latest commit on master.
commit: 78983e939ab17f02f8911c8b0d0e326b419856b9

Comment 3 Saul Wold 2012-11-07 14:35:21 UTC

This needs to be well documentated that bitbake does not handle "Spaces" in 
directory names, linux just does not
handle this gracefully.

It's possible a check could be added for spaces in the filename.

Comment 4 Richard Purdie 2012-11-07 14:41:04 UTC

To be clear this is not a linux issue, the biggest problem is autotools doesn't handle this correct. If autotools did handle it correctly, there would be hope for the rest of the system. it doesn't and therefore we won't until it does.

Comment 5 Scott Rifenbark 2012-11-09 14:28:25 UTC

I will figure out a spot to put some notes and such in the documentation warning the user about this problem.  I am assuming the suggested action for the user is simply to be sure that the drive and filesystem that the user is using for the poky clone shoud be free of spaces in directory names. 

Scott

Comment 6 Scott Rifenbark 2012-11-09 15:37:35 UTC

Notes added in the following places:

* http://www.yoctoproject.org/docs/1.4/poky-ref-manual/poky-ref-manual.html#ref-structure

* http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#source-directory

* http://www.yoctoproject.org/docs/1.4/poky-ref-manual/poky-ref-manual.html#structure-core-script

* http://www.yoctoproject.org/docs/1.4/yocto-project-qs/yocto-project-qs.html#building-image  (I did not place a note here since it would add clutter to the QS.  Instead, I provided a cross-link into the reference manual to the oe-init-build-env section).

* http://www.yoctoproject.org/docs/1.4/poky-ref-manual/poky-ref-manual.html#structure-core-script (link only)

Let me know if this is adequate.

Scott

Comment 7 Scott Rifenbark 2012-11-16 00:30:22 UTC

No feedback indicating problems with this solution. Marked RESOLVED.  See Comment #6 for the links to the final text. 

Scott

Comment 8 Saul Wold 2013-01-19 00:01:28 UTC

*** Bug 3759 has been marked as a duplicate of this bug. ***

Comment 9 Alexandru Georgescu 2013-04-17 13:40:15 UTC

verified as per above comments.