Bug 4772 - When the project directory path contain @ character, the build fails
Summary: When the project directory path contain @ character, the build fails
Status: VERIFIED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-06-25 06:05 UTC by Li Wang
Modified: 2013-10-02 09:51 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Li Wang 2013-06-25 06:05:02 UTC
1. reproduce steps:
# mkdir poky_project@
# cd poky_project@
# source  /your/poky/path/oe-init-build-env
# bitbake xxx
2.
fail to build, when do_fetch package.
3.
in wr product, fail to configure.
Comment 1 Richard Purdie 2013-06-25 14:56:44 UTC
We don't support the @ in build directories. We should add this to the sanity checks already made for build paths and inform the user this is an unacceptable path at which point this bug can be resolved.
Comment 2 Richard Purdie 2013-06-28 09:26:48 UTC
Fixed in master http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=4707a74db3822f5ad26e720fa47dd011c5d32a1c so we now get an error message if this happens.
Comment 3 Razvan Ionescu 2013-10-02 09:51:27 UTC
Verified with: poky: 4707a74db3822f5ad26e720fa47dd011c5d32a1c

Now the error message is displayed as follows:

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Error, you have an invalid character (@) in your COREBASE directory path. Please move the installation to a directory which doesn't include any @ characters.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed