diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-07-05 16:35:03 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-07-07 10:49:30 +0100 |
| commit | 512be74ee0d7ad7e76c1be62d1e0f499aa51d174 (patch) | |
| tree | ea98570898dff17b8d69db488dfa9044917f21ec /meta/conf/machine | |
| parent | 1b44053f6c4ac33d5058183e6634b1ba831ae601 (diff) | |
| download | openembedded-core-512be74ee0d7ad7e76c1be62d1e0f499aa51d174.tar.gz openembedded-core-512be74ee0d7ad7e76c1be62d1e0f499aa51d174.tar.bz2 openembedded-core-512be74ee0d7ad7e76c1be62d1e0f499aa51d174.tar.xz openembedded-core-512be74ee0d7ad7e76c1be62d1e0f499aa51d174.zip | |
kernel-yocto: Fix case where recipe is always reparsed
If you include a bitbake variable as a comment in a shell function
then it gets expanded by the bitbake signature handling code.
This could be classed as a bug or a feature depending on your viewpoint
(e.g. a multiline variable included in a comment could actually contain
executable code).
Since we don't always want kernel-yocto to reparse this changes the
syntax of the comment so it doesn't trigger the problem.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/machine')
0 files changed, 0 insertions, 0 deletions