linux/meta-openembedded.git/meta-oe/recipes-benchmark/nbench-byte, branch kirkstone

nbench-byte: update SRC_URI

2019-03-20T04:00:06+00:00

Signed-off-by: Oliver Friedrich Signed-off-by: Matthias Schiffer Signed-off-by: Khem Raj

nbench-byte: Dont append cflags to cc

2018-05-23T22:32:05+00:00

adding cflags is redundant Signed-off-by: Khem Raj

nbench-byte: Update SRC_URI to fossies.org

2017-10-02T12:34:40+00:00

Current SRC_URI responds with 404 Fix WARNING: nbench-byte-2.2.3-r0 do_fetch: Failed to fetch URL http://www.tux.org/~mayer/linux/nbench-byte-2.2.3.tar.gz, attempting MIRRORS if available Signed-off-by: Khem Raj Signed-off-by: Martin Jansa

nbench-byte: Explicitly set EXTRA_OEMAKE as required

2016-02-15T09:16:38+00:00

This recipe currently relies on EXTRA_OEMAKE having been to set to "-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this explicit so that the default in bitbake.conf can be changed. Signed-off-by: Mike Crowe Signed-off-by: Martin Jansa

nbench-byte: Fix license QA error

2014-12-31T15:32:30+00:00

The license is not a common only and seems to be a 'free distribution' license but without explicit rules about modification or similar. Due that, we copied the license text from the README file and added it onto nbench-byte license file. This fixes following QA error: ,---- | WARNING: Recipe nbench-byte, LICENSE (freely distributable) has | invalid format, LICENSES must have operator "([&|() ])" between | them. `---- Signed-off-by: Otavio Salvador Signed-off-by: Martin Jansa

meta-oe: use BPN in SRC_URI

2014-07-15T12:56:55+00:00

Fixed SRC_URI: * ${PN} -> ${BPN}, use ${BP} if it was ${PN}-${PV} * ${P} -> ${BP} Otherwise we would meet do_fetch errors when we do the multilib, native or nativesdk build. Signed-off-by: Robert Yang Signed-off-by: Martin Jansa

nbench-byte: Fix parallel building error

2014-06-13T11:38:10+00:00

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* 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 Acked-by: Koen Kooi

nbench-byte-2.3.3: import recipe from oe-classic

2012-02-29T13:52:45+00:00

* Import the nbench-byte recipe from the oe-classic git repo at git://git.openembedded.org/openembedded commit id: * 6fe7cef27069415f2eba36bc640cf59013d4979b * Update LICENSE checksums * Tested on an AM335x EVM which is the same processor as the beaglebone. * Original Author: * Marcin Juszkiewicz * Modifications by: * Koen Kooi * Martin Jansa * Chris Larson Signed-off-by: Chase Maupin Signed-off-by: Koen Kooi