| Age | Commit message (Collapse) | Author |
|---|
|
The existing conditions for ppc64/be are applicable for le as well
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
patching file configure
Hunk #1 succeeded at 535 with fuzz 1 (offset 96 lines).
Signed-off-by: Armin Kuster <akuster808@gmail.com>
|
|
ERROR: concurrencykit-0.5.1+gitAUTOINC+f97d3da5c3-r0 do_fetch: Function failed: Fetcher failure for URL: 'git://github.com/concurrencykit/ck.git;protocol=https'. Unable to fetch URL from any source.
removed "protocol=https"
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* with newer bitbake it parses it differently and task fails:
concurrencykit/0.4.3+gitAUTOINC+900d203aa9-r0/temp/run.do_configure.13244:
Syntax error: end of file unexpected (expecting "}")
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
It's not necessary to specify the protocol parameter when it's the
default protocol for the fetcher, e.g. the default protocol for
git fetcher it git, "protocol=git" isn't needed.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
Provides concurrency primitives
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
Khem Raj
Armin Kuster
Derek Straka
Martin Jansa
Jackie Huang