Bug 119 - Ensure the correct (bash) shell is used when spawning shells
Summary: Ensure the correct (bash) shell is used when spawning shells
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Low normal
Target Milestone: 1.0 M1
Assignee: Joshua Lock - Disabled
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-07-16 05:03 UTC by Joshua Lock - Disabled
Modified: 2011-07-25 08:21 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock - Disabled 2010-07-16 05:03:07 UTC
running on a system with SHELL set to something other than bash (i.e. fish) causes issues when spawning a shell.
Comment 1 Saul Wold 2010-08-25 09:28:13 UTC
Is this being fixed as part of Checksumming??  If so, can you mark it as accepted and comment it.

Thanks
   Sau!
Comment 2 Richard Purdie 2011-02-22 03:17:09 UTC
Checksumming doesn't specifically fix this. We currently don't force any particular shell for the build and probably should.
Comment 3 Joshua Lock - Disabled 2011-02-23 03:22:24 UTC
Patch resolution should always spawn with bash as meta/lib/oe/patch.py sets SHELLCMDS to bash:

os.environ['SHELLCMDS'] = "bash --rcfile " + rcfile

Which leaves the devshell and kernel classes spawning terminals with the default shell.

I'm working on a patch.
Comment 4 Joshua Lock - Disabled 2011-02-24 07:59:55 UTC
My patch has been merged to master.

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=6d261a50bac760b55e33c303e9f3f2214338eb4f
Comment 5 Joshua Lock - Disabled 2011-07-25 08:21:50 UTC
Verify fixed