date:20170719

[yocto] QA cycle report for 2.3.1 rc2

2017-07-19 Thread Cruz, Libertad

Hello All,



Here is the report for the 2.3.1 rc2 full point release test cycle.

Full Report : 
https://wiki.yoctoproject.org/wiki/WW29_-_2017-07-18-_Full_Test_Cycle_-_2.3.1_rc2#Testing_data



=== Summary 

The QA cycle for release 2.3.1 rc2 is complete, no blockers. 10832 [3] was 
reopened after issue reappeared when trying to install eSDK. Only one new bug 
about tcf-agent daemon not being able to be stopped. [1]



There was a 8.05% regression on building rootfs in Fedora 23. The performance 
test results for Ubuntu 15 are misleading because there is a problem with the 
machine running the OS, this is currently being investigated by the QA team.



For ptest there was an improvement of the pass rate for gdk-pixbuf of 5% an 
improvement of 1.30% of valgrind. On the other side there was a regression on 
the pass rate of libxml2 of 1.20% [5], on openssh of 2.9%[6] and on busybox of 
0.20%[4].



QA-Hint: QA sees no mayor issues, blockers on this point release. Current bugs 
don't block full functionalities, on any component.



   New Bugs
-11795 [Yocto 2.3.1] Can not stop tcf-agent daemon [1]
-11811 - ptest-busybox
-11812 - ptest- libxml2 cases failed
-11813 - ptest- openssh

  * M+ bugs
- 10477 yocto-bsp: tool should output a conf file to be consume by 
the qemu runner [2]

- 10832  eSDK install script failed with "tasks executed 
unexpectedly" messages [3]





Full Bug Report : 
https://wiki.yoctoproject.org/wiki/WW29_-_2017-07-18-_Full_Test_Cycle_-_2.3.1_rc2#Bugs_Found_during_QA_Test





 Links =



1.https://bugzilla.yoctoproject.org/show_bug.cgi?id=11795 
 [1]

2.https://bugzilla.yoctoproject.org/show_bug.cgi?id=10477 
 [2]

3.https://bugzilla.yoctoproject.org/show_bug.cgi?id=10832 
 [3]

4.https://bugzilla.yoctoproject.org/show_bug.cgi?id=11811 
 [4]

5.https://bugzilla.yoctoproject.org/show_bug.cgi?id=11812 
 [5]

6.https://bugzilla.yoctoproject.org/show_bug.cgi?id=11813 [6]











Regards

Libertad G.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [dizzy] php 5.4.36 compilation with postgresql 9.3.4

2017-07-19 Thread kris duff

Hello,
For a few weeks (part time) I am trying to add to my image php support (under 
lighttpd/fastcgi) with postgresql support.
The php module can get compiled and used without pgsql support.
I have created a php_5.4.36.bbappend file that contains this :
-FILES_${PN} += 
"/usr/lib"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

export LPQLIBDIR = "${STAGING_LIBDIR}"
export LPQINCLUDEDIR = "${STAGING_INCDIR}"  DEPENDS = "postgresql 
postgresql-native pg-config-custom"
EXTRA_OECONF += " --with-pgsql=${STAGING_DIR_TARGET}${EXEC_PREFIX} 
--with-pdo-pgsql=${D}${bindir}"
-

I know, I should have used PACKAGECONFIG[pgsql] but in my case I prefer not 
touching local.conf.
when I bitbake my image, I see the following message :
ERROR: This autoconf log indicates errors, it looked at host include and/or 
library paths while determining system capabilities.Rerun configure task after 
fixing this. The path was 
'/home/yocto/build/tmp/work/core2-64-poky-linux/php/5.4.36-r0/build'ERROR: 
Function failed: do_qa_configure
from my reading, the problem could be here :checking for pkg-config... 
/home/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/pkg-configconfigure: 
WARNING: using cross tools not prefixed with host triplet
other than that, looked in the compile log file to find "'CROSS COMPILE 
Badness:' or 'is unsafe for cross-compilation'"... as seen in insane.bbclass. 
and found nothing.
How to solve this issue ? Anyone has been able to connect php with pgsql ?
Thank you
Regards
Kris

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] do_compile errors.

2017-07-19 Thread Joseph Ngigi

Here's my console output:

ngigijoe@ngigijoe-HP-2000-Notebook-PC:~/src/git/pyro/poky/cubieboard2$
bitbake core-image-sato
Loading cache: 100%
|#|
Time: 0:00:00
Loaded 2168 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal-4.8"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "cubieboard2"
DISTRO= "poky"
DISTRO_VERSION= "2.3.1"
TUNE_FEATURES = "arm armv7ve vfp neon vfpv4 callconvention-hard
cortexa7"
TARGET_FPU= "hard"
meta
meta-poky = "pyro:6bd890d9e011014cf323e61267f8b256949d44aa"
meta-sunxi= "pyro:0056643fcf2c496a0f2cf005fb67d626ab0e2c10"
meta-oe
meta-gnome= "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"

Initialising tasks: 100%
||
Time: 0:00:19
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: gperf-native-3.0.4-r0 do_compile: oe_runmake failed
ERROR: gperf-native-3.0.4-r0 do_compile: Function failed: do_compile (log
file is located at
/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/temp/log.do_compile.7266)
ERROR: Logfile of failure stored in:
/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/temp/log.do_compile.7266
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 8
| ERROR: oe_runmake failed
| cd lib; make all
| make[1]: Entering directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/lib'
| make[1]: Nothing to be done for 'all'.
| make[1]: Leaving directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/lib'
| cd src; make all
| make[1]: Entering directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/src'
| g++
-isystem/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/include
-O2 -pipe -D_GLIBCXX_USE_CXX11_ABI=0
-L/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/lib
-L/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/lib
-Wl,-rpath-link,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/lib
-Wl,-rpath-link,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/lib
-Wl,-rpath,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/lib
-Wl,-rpath,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/lib
-Wl,-O1 -o gperf version.o positions.o options.o keyword.o keyword-list.o
input.o bool-array.o hash-table.o search.o output.o main.o ../lib/libgp.a
-lm
| g++: error: version.o: No such file or directory
| g++: error: positions.o: No such file or directory
| g++: error: options.o: No such file or directory
| g++: error: keyword.o: No such file or directory
| g++: error: keyword-list.o: No such file or directory
| g++: error: input.o: No such file or directory
| g++: error: bool-array.o: No such file or directory
| g++: error: hash-table.o: No such file or directory
| g++: error: output.o: No such file or directory
| g++: error: main.o: No such file or directory
| g++: error: ../lib/libgp.a: No such file or directory
| Makefile:74: recipe for target 'gperf' failed
| make[1]: *** [gperf] Error 1
| make[1]: Leaving directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/src'
| Makefile:33: recipe for target 'all' failed
| make: *** [all] Error 2
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/temp/log.do_compile.7266)
ERROR: Task
(virtual:native:/home/ngigijoe/src/git/pyro/poky/meta/recipes-extended/gperf/gperf_3.0.4.bb:do_compile)
failed with exit code '1'

Second Keyboard Interrupt, stopping...


Summary: 1 task failed:

virtual:native:/home/ngigijoe/src/git/pyro/poky/meta/recipes-extended/gperf/gperf_3.0.4.bb:
do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
NOTE: Sending SIGTERM to remaining 6 tasks


On Wed, Jul 19, 2017 at 3:58 PM, Joseph Ngigi  wrote:

> I seem to be having a lot of do_compile failure errors, building
> core-image-sato for cubieboard2 using poky pyro. I do not understand
> whether it is a gcc com

Re: [yocto] Error while integrating PyPy module in Yocto (Jethro branch) build.

2017-07-19 Thread Leonardo Sandoval

On Wed, 2017-07-19 at 12:39 +, JAYMIN DABHI wrote:
> Hi All,
> 
> I am trying to integrate PyPy in my current Yocto (Jethro branch)
> build for my i.MX6UL processor based development board. The board has
> "armv7a" (cortexa7) architecture. 
> 
> I am using "meta-pypy" layer from here and inherit the pypy package in
> my local.conf.
> But, it gives me error during bitbaking. I am bitbaking the
> "core-image-base".
> The error is as below :
> ERROR: Fetcher failure: Unable to find file 
> file://pypy-4.0.1-cortexa7.tar.bz2 anywhere.
> I think, it can't find the package "pypy-4.0.1-cortexa7.tar.bz2" in
> pypy directory.


Make sure the is the proper ARCH tarball in the recipes/pypy/pypy
folder. If not there, then the layer does not support that architecture.

leo
> 
> What should be the other possible reason? and How it can be solved?
> 
> 
> Suggestions are welcome.
> 
> 
> Thanks,
> -
> JAYMIN
> 
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] do_compile errors.

2017-07-19 Thread Joseph Ngigi

I seem to be having a lot of do_compile failure errors, building
core-image-sato for cubieboard2 using poky pyro. I do not understand
whether it is a gcc compiler issue or any other problem. Any assistance
will be highly appreciated.

Below is my logfile.

DEBUG: Executing shell function do_compile
NOTE: make -j 8
ERROR: oe_runmake failed
cd lib; make all
make[1]: Entering directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/lib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/lib'
cd src; make all
make[1]: Entering directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/src'
g++
-isystem/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/include
-O2 -pipe -D_GLIBCXX_USE_CXX11_ABI=0
-L/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/lib
-L/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/lib
-Wl,-rpath-link,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/lib
-Wl,-rpath-link,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/lib
-Wl,-rpath,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/usr/lib
-Wl,-rpath,/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/recipe-sysroot-native/lib
-Wl,-O1 -o gperf version.o positions.o options.o keyword.o keyword-list.o
input.o bool-array.o hash-table.o search.o output.o main.o ../lib/libgp.a
-lm
g++: error: version.o: No such file or directory
g++: error: positions.o: No such file or directory
g++: error: options.o: No such file or directory
g++: error: keyword.o: No such file or directory
g++: error: keyword-list.o: No such file or directory
g++: error: input.o: No such file or directory
g++: error: bool-array.o: No such file or directory
g++: error: hash-table.o: No such file or directory
g++: error: output.o: No such file or directory
g++: error: main.o: No such file or directory
g++: error: ../lib/libgp.a: No such file or directory
Makefile:74: recipe for target 'gperf' failed
make[1]: *** [gperf] Error 1
make[1]: Leaving directory
'/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/src'
Makefile:33: recipe for target 'all' failed
make: *** [all] Error 2
ERROR: Function failed: do_compile (log file is located at
/home/ngigijoe/src/git/pyro/poky/cubieboard2/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/temp/log.do_compile.600)

-- 
J.W.Ngigi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Error while integrating PyPy module in Yocto (Jethro branch) build.

2017-07-19 Thread JAYMIN DABHI

Hi All,
 I am trying to integrate PyPy in my current Yocto (Jethro branch) build for my 
i.MX6UL processor based development board. The board has "armv7a" (cortexa7) 
architecture. 
 I am using "meta-pypy" layer from here (https://github.com/mzakharo/meta-pypy) 
and inherit the pypy package in my local.conf.
 But, it gives me error during bitbaking. I am bitbaking the "core-image-base".
 The error is as below :
ERROR: Fetcher failure: Unable to find file 
file://pypy-4.0.1-cortexa7.tar.bz2 anywhere.  I think, it can't find the 
package "pypy-4.0.1-cortexa7.tar.bz2" in pypy directory.
 What should be the other possible reason? and How it can be solved?

 Suggestions are welcome.

 Thanks,
-
JAYMIN
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dynamic layer dependencies in meta-security

2017-07-19 Thread Mark Hatle

On 7/19/17 1:57 AM, Patrick Ohly wrote:
> Hello Armin!
> 
> I'm trying to use the latest meta-security master in refkit. Refkit runs
> yocto-compat-layer.py against its own layers, which then pulls in
> meta-security as one of the dependencies. That's where I am hitting a
> snag:
> 
> INFO: Detected layers:
> INFO: meta-refkit: LayerType.DISTRO, 
> /fast/work/intel-iot-refkit-pr/meta-refkit
> INFO: 
> INFO: Setting up for meta-refkit(LayerType.DISTRO), 
> /fast/work/intel-iot-refkit-pr/meta-refkit
> INFO: Adding layer dependency meta-selftest
> INFO: Adding layer dependency meta-intel
> INFO: Adding layer dependency meta-refkit-gateway
> INFO: Adding layer dependency meta-refkit-core
> INFO: Adding layer dependency meta-oic
> INFO: Adding layer dependency meta-iot-web
> INFO: Adding layer dependency meta-refkit-computervision
> INFO: Adding layer dependency meta-intel-realsense
> INFO: Adding layer dependency meta-clang
> INFO: Adding layer dependency meta-oe
> INFO: Adding layer dependency meta-refkit-industrial
> INFO: Adding layer dependency meta-python
> INFO: Adding layer dependency meta-ros
> INFO: Adding layer dependency meta-iotqa
> INFO: Adding layer dependency meta-security
> INFO: Adding layer dependency meta-perl
> INFO: Adding layer dependency meta-security-isafw
> INFO: Adding layer dependency meta-filesystems
> INFO: Adding layer dependency meta-gnome
> INFO: Adding layer dependency meta-networking
> INFO: Adding layer dependency meta-flatpak
> Traceback (most recent call last):
>   File 
> "/fast/work/intel-iot-refkit-pr/openembedded-core/scripts/yocto-compat-layer.py",
>  line 203, in 
> ret =  main()
>   File 
> "/fast/work/intel-iot-refkit-pr/openembedded-core/scripts/yocto-compat-layer.py",
>  line 151, in main
> if not add_layer_dependencies(bblayersconf, layer, dep_layers, logger) or 
> \
>   File 
> "/fast/work/intel-iot-refkit-pr/openembedded-core/scripts/lib/compatlayer/__init__.py",
>  line 195, in add_layer_dependencies
> output = check_command('Getting existing layers failed.', 'bitbake-layers 
> show-layers').decode('utf-8')
>   File 
> "/fast/work/intel-iot-refkit-pr/openembedded-core/scripts/lib/compatlayer/__init__.py",
>  line 228, in check_command
> raise RuntimeError(msg)
> RuntimeError: Getting existing layers failed.
> Command: bitbake-layers show-layers
> Output:
> ERROR: Layer 'security' depends on layer 'xfce-layer', but this layer is not 
> enabled in your configuration
> 
> The reason is the way how meta-security declares its dependencies:
> 
> LAYERDEPENDS_security = "core openembedded-layer perl-layer"
> LAYERDEPENDS_security += "${@bb.utils.contains("DISTRO_FEATURES", "x11", 
> "gnome-layer xfce-layer", "", d)}"
> LAYERDEPENDS_security += "${@bb.utils.contains("MACHINE_FEATURES", "tpm", 
> "tpm-layer", "",d)}"
> LAYERDEPENDS_security += "${@bb.utils.contains("MACHINE_FEATURES", "tpm2", 
> "tpm-layer", "",d)}"
> LAYERDEPENDS_security += "${@bb.utils.contains("MACHINE_FEATURES", "vtpm", 
> "tpm-layer meta-filesystems", "",d)}"
> 
> I haven't checked how exactly yocto-compat-layer.py deals with this, but
> the end result is that it doesn't add meta-xfce when adding
> meta-security. Then when "bitbake-layers show-layers" is called, a
> distro (poky) has been chosen where x11 is in DISTRO_FEATURES, causing
> the dependency check to fail.

The meta-freescale method of checking if a layer is present and adding features
is how they resolve this issue.  Instead of making it a dependency, they simply
check if it's already present and then add to it.

I agree the above is less then optimal way of doing things, and will prevent the
layer index from getting a clear list of what may be required.

Note, there is also LAYERRECOMMENDS_... in this case, the system could recommend
gnome-layer, xfce-layer, tpm-layer, meta-filesystems, and then use the
meta-freescale approach to only enabling thsoe features if the recommended
layers are present.

> This highlights a conceptual issue with the dynamic
> LAYERDEPENDS_security above: which distro or machine config is active?
> Tools like yocto-compat-layer.py or the layer index have to do their
> work before that is defined.
> 
> This is also problematic with multiconfig. The same bblayers.conf might
> be used with one config where x11 is off and another where it is on.
> 
> I suspect LAYERDEPENDS simply can't be dynamic. It either has to include
> everything that a layer might depend on (even when the additional
> content doesn't end up being used), or it just depends on the essential
> parts and then enables additional recipes only when the optional layers
> they depend on are present. BBFILES_DYNAMIC can be used for that, or the
> recipes themselves check BBCOLLECTIONS in anonymous python code and
> raise a SkipRecipe exception when their pre-condition isn't satisfied.
> 
> Copying Paul (layer index) and Mark (oe-yocto-compat.py, setup tool) for
> their input.

I would certainly caution against dynamic layerdepends/la

Re: [yocto] [yocto-autobuilder][PATCHv3 5/5] buildset-config.yocto-qa: Add intel-corei7-64-daft buildset

2017-07-19 Thread Victor Rodriguez

On Tue, Jul 18, 2017 at 11:14 AM, Aníbal Limón  wrote:

> This buildset is for support running sanity tests over a DUT like
> Minnowboard for the moment only builds core-image-sato, there is a need
> to make it configurable.
>
> Also the listo of the available devices are fixed into the UI as
> parameters.
>
> [YOCTO #10604]
>
> Signed-off-by: Aníbal Limón 
> ---
>  buildset-config.yocto-qa/intel-corei7-64-daft.conf | 59
> ++
>  1 file changed, 59 insertions(+)
>  create mode 100644 buildset-config.yocto-qa/intel-corei7-64-daft.conf
>
> diff --git a/buildset-config.yocto-qa/intel-corei7-64-daft.conf
> b/buildset-config.yocto-qa/intel-corei7-64-daft.conf
> new file mode 100644
> index 000..cb3bcdade75
> --- /dev/null
> +++ b/buildset-config.yocto-qa/intel-corei7-64-daft.conf
> @@ -0,0 +1,59 @@
> +[intel-corei7-64-daft]
> +builders: 'example-worker'
> +repos: [{'poky':
> +{'repourl':'git://git.yoctoproject.org/poky',
> + 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp',
> 'yocto':'meta-yocto', 'poky':'meta-poky'},
> + 'branch':'master'}},
> +{'meta-intel':
> +{'repourl':'git://git.yoctoproject.org/meta-intel',
> + 'layerversion':{'intel':'meta-intel'},
> + 'branch':'master'}}]
> +props: [{'kmeta':{'prop_type':'StringParameter',
> +   'size': 15,
> +   'name': 'kmeta',
> +   'default': '',
> +   'label':' branch for KMETA_${MACHINE}
> (default is blank):'}},
> +{'srcrev_meta':{'prop_type':'StringParameter',
> +   'size': 15,
> +   'name': 'srcrev_meta',
> +   'default': '${AUTOREV}',
> +   'label':' SRCREV for KMETA_${MACHINE}
> (default is ${AUTOREV}):'}},
> +{'srcuri_meta':{'prop_type':'StringParameter',
> +   'size': 50,
> +   'name': 'srcuri_meta',
> +   'default': '',
> +   'label':' SRC_URI_pn-linux-yocto KMETA
> append. (default is blank). This should be constructed as *just* the
> git uri portion of the string. (git://git.yoctoproject.
> org/linux-yocto-3.19.git'}},
> +{'kbranch':{'prop_type':'StringParameter',
> +   'size': 15,
> +   'name': 'kbranch',
> +   'default': '',
> +   'label':' branch for KBRANCH_${MACHINE}
> (default is blank):'}},
> +{'srcrev_machine':{'prop_type':'StringParameter',
> +   'size': 15,
> +   'name': 'srcrev_machine',
> +   'default': '${AUTOREV}',
> +   'label':' SRCREV for KBRANCH. (default is
> ${AUTOREV}):'}},
> +{'srcuri_machine':{'prop_type':'StringParameter',
> +   'size': 50,
> +   'name': 'srcuri_machine',
> +   'default': '',
> +   'label':' SRC_URI_pn-linux-yocto KBRANCH
> append. (default is blank). This should be constructed as *just* the
> git uri portion of the string. (git://git.yoctoproject.
> org/linux-yocto-3.19.git'}},
> +   {'dut':{'prop_type':'ChoiceStringParameter',
> +  'choices': ['Minnowboard1'],
> +  'name': 'dut',
> +  'label':'Selects DUT for flashing.'}}]
> +steps: [{'SetDest':{}},
> +{'CheckOutLayers': {}},
> +{'RunPreamble': {}},
> +{'CheckBSPExists': {}},
> +{'GetDistroVersion' : {'distro': 'poky'}},
> +{'CreateAutoConf': {'machine': 'intel-corei7-64', 'SDKMACHINE' :
> 'x86_64',
> +'distro': 'poky'}},
> +{'CreateBBLayersConf': {'buildprovider' : 'yocto',
> +'bsplayer': True, 'bspprovider': 'intel',
> +'layerdirs': ['meta-intel',
> 'meta-intel/meta-tlk']}},
> +{'AddKernelProps': {}},
> +{'DaftGetDevices': {}},
> +{'BuildImages': {'images': 'core-image-sato'}},
> +{'DaftFlash':{}},
> +{'RunSanityTests': {'images': 'core-image-sato'}},]
> --
> 2.11.0
>
> Is there any documentation for this , i like a lot the idea and i would
like to know how to test this



> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Help Compiling vlc for i.MX6 SABRE-SD

2017-07-19 Thread victor_wang.Winmate

Hi,

 

I am new in Yocto, I have to admit it, please be patient with my stupid 
questions.

I built vlc on meta-fsl-arm layers and fsl-imx-x11 distro on machine 
imx6dlsabresd.

I used commend `bitbake vlc` to build it and will get errors like bellow link.

 

https://gist.github.com/victorwangwinmate/3fb03f42a47f3405b5aef05c3ac47bdc

 

After some googling, I try to modify my local.conf like bellow link.

 

https://gist.github.com/victorwangwinmate/3593c1c63cf96a0d44537a24cc6d17c5

 

And I try to build the image with this commend `bitbake –C compile 
fsl-image-gui `

Unfortunately, I will get the same error as the first link.

 

The first question is why it will show the error that one of 
libjpeg-turbo_8d+1.4.1.bb and jpeg_9a.bb is missing something.

The second is which one I should use and how?

The third is how can I fix this error in the proper way?

 

Please help

 

Thanks in advance

Best Regards

Victor Wang

=

Winmate Commuication INC.

  Tel:+886-2-8511-0288 ext 878; Fax:+886-2-85110211

✉   victor_w...@winmate.com.tw

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.3.1 rc2

[yocto] [dizzy] php 5.4.36 compilation with postgresql 9.3.4

Re: [yocto] do_compile errors.

Re: [yocto] Error while integrating PyPy module in Yocto (Jethro branch) build.

[yocto] do_compile errors.

[yocto] Error while integrating PyPy module in Yocto (Jethro branch) build.

Re: [yocto] dynamic layer dependencies in meta-security

Re: [yocto] [yocto-autobuilder][PATCHv3 5/5] buildset-config.yocto-qa: Add intel-corei7-64-daft buildset

[yocto] Help Compiling vlc for i.MX6 SABRE-SD

9 matches

Site Navigation

Mail list logo

Footer information