Re: [yocto] New error in 1.7

[peterengcomau001]

thank you. i have fixed the curl problem but a new problem has occured
with the build. This problem did not appear in v1.6.1. The problem is:

lachlan@lachlan-SVP13215PXB:~/poky/build-atmel$ bitbake
atmel-qt5-demo-image -c populate_sdk  

Loading cache: 100%
|###|
ETA: 00:00:00  

Loaded 2108 entries from dependency cache.  

NOTE: Resolving any missing task queue dependencies  

Build Configuration:  

BB_VERSION = "1.24.0"  

BUILD_SYS = "x86_64-linux"  

NATIVELSBSTRING = "Ubuntu-14.04"  

TARGET_SYS = "arm-poky-linux-gnueabi"  

MACHINE = "sama5d3xek"  

DISTRO = "poky"  

DISTRO_VERSION = "1.7"  

TUNE_FEATURES = "arm armv7a vfp thumb callconvention-hard cortexa5" 


TARGET_FPU = "vfp"  

meta-atmel = "my_branch:711809b0d91f816b10e70508986b3f43098000ba"  

meta-qt5 = "my_branch:0732e184acef5e0200f46d7f95702774e5de1904"  

meta  

meta-yocto  

meta-yocto-bsp = "dizzy:db7f4f31c915a59c502cac4be905d23df5246b3d"  

meta-oe  

meta-python  

meta-networking  

meta-ruby = "my_branch:9efaed99125b1c4324663d9a1b2d3319c74e7278"  

NOTE: Preparing runqueue  

NOTE: Executing SetScene Tasks  

NOTE: Executing RunQueue Tasks  

ERROR: Function failed: do_configure (log file is located at
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_configure.5736)
 

ERROR: Logfile of failure stored in:
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_configure.5736
 

Log data follows:  

| DEBUG: Executing python function sysroot_cleansstate  

| DEBUG: Python function sysroot_cleansstate finished  

| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
'common']  

| DEBUG: Executing shell function autotools_preconfigure  

| DEBUG: Shell function autotools_preconfigure finished  

| DEBUG: Executing python function autotools_copy_aclocals  

| DEBUG: Python function autotools_copy_aclocals finished  

| DEBUG: Executing shell function do_configure  

| automake (GNU automake) 1.14.1  

| Copyright (C) 2013 Free Software Foundation, Inc.  

| License GPLv2+: GNU GPL version 2 or later   

| This is free software: you are free to change and redistribute it.
 

| There is NO WARRANTY, to the extent permitted by law.  

|  

| Written by Tom Tromey   

| and Alexandre Duret-Lutz .  

| AUTOV is 1.14  

| NOTE: Executing ACLOCAL="aclocal
--system-acdir=/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/aclocal-copy/
--automake-acdir=/home/lachlan/poky/build-atmel/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.14"
autoreconf --verbose --install --force --exclude=autopoint -I
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/
 

| autoreconf: Entering directory `'  

| autoreconf: configure.ac: not using Gettext  

| autoreconf: running: aclocal
--system-acdir=/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/aclocal-copy/
--automake-acdir=/home/lachlan/poky/build-atmel/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.14
-I
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/
-I
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/
--force -I m4 -I common/m4  

| autoreconf: configure.ac: tracing  

| autoreconf: running: libtoolize --copy --force  

| libtoolize: putting auxiliary files in `.'.  

| libtoolize: copying file `./ltmain.sh'  

| libtoolize: putting macros in `m4'.  

| libtoolize: copying file `m4/libtool.m4'  

| libtoolize: copying file `m4/ltoptions.m4'  

| libtoolize: copying file `m4/ltsugar.m4'  

| libtoolize: copying file `m4/ltversion.m4'  

| libtoolize: copying file `m4/lt~obsolete.m4'  

| libtoolize: Remember to add `LT_INIT' to configure.ac.  

| libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to
configure.ac and  

| libtoolize: rerunning libtoolize, to keep the correct libtool
macros in-tree  

| autoreconf: running:
/home/lachlan/poky/build-atmel/tmp/sysroo

Re: [yocto] New error in 1.7

[Paul Eggleton]

Hi there,

On Tuesday 25 November 2014 19:27:13 peterengcomau...@adam.com.au wrote:
> thank you. i have fixed the curl problem but a new problem has occured
> with the build. This problem did not appear in v1.6.1. The problem is:
> 
>   lachlan@lachlan-SVP13215PXB:~/poky/build-atmel$ bitbake
> atmel-qt5-demo-image -c populate_sdk
> 
>   Loading cache: 100%
> 
> |###
> |###
> |#|
> ETA: 00:00:00
> 
>   Loaded 2108 entries from dependency cache.
> 
>   NOTE: Resolving any missing task queue dependencies
> 
>   Build Configuration:
> 
>   BB_VERSION = "1.24.0"
> 
>   BUILD_SYS = "x86_64-linux"
> 
>   NATIVELSBSTRING = "Ubuntu-14.04"
> 
>   TARGET_SYS = "arm-poky-linux-gnueabi"
> 
>   MACHINE = "sama5d3xek"
> 
>   DISTRO = "poky"
> 
>   DISTRO_VERSION = "1.7"
> 
>   TUNE_FEATURES = "arm armv7a vfp thumb callconvention-hard cortexa5"
> 
> 
>   TARGET_FPU = "vfp"
> 
>   meta-atmel = "my_branch:711809b0d91f816b10e70508986b3f43098000ba"
> 
>   meta-qt5 = "my_branch:0732e184acef5e0200f46d7f95702774e5de1904"
> 
>   meta
> 
>   meta-yocto
> 
>   meta-yocto-bsp = "dizzy:db7f4f31c915a59c502cac4be905d23df5246b3d"
> 
>   meta-oe
> 
>   meta-python
> 
>   meta-networking
> 
>   meta-ruby = "my_branch:9efaed99125b1c4324663d9a1b2d3319c74e7278"
> 
>   NOTE: Preparing runqueue
> 
>   NOTE: Executing SetScene Tasks
> 
>   NOTE: Executing RunQueue Tasks
> 
>   ERROR: Function failed: do_configure (log file is located at
> /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
> gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_configure.5736)
> 
> 
>   ERROR: Logfile of failure stored in:
> /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
> gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_configure.5736
>   Log data follows:
>   | DEBUG: Executing python function sysroot_cleansstate
>   | 
>   | DEBUG: Python function sysroot_cleansstate finished
>   | 
>   | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
> 
> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
> 'common']
> 
>   | DEBUG: Executing shell function autotools_preconfigure
>   | 
>   | DEBUG: Shell function autotools_preconfigure finished
>   | 
>   | DEBUG: Executing python function autotools_copy_aclocals
>   | 
>   | DEBUG: Python function autotools_copy_aclocals finished
>   | 
>   | DEBUG: Executing shell function do_configure
>   | 
>   | automake (GNU automake) 1.14.1
>   | 
>   | Copyright (C) 2013 Free Software Foundation, Inc.
>   | 
>   | License GPLv2+: GNU GPL version 2 or later
>   | 
>   | This is free software: you are free to change and redistribute it.
>   | 
>   | 
>   | There is NO WARRANTY, to the extent permitted by law.
>   | 
>   | 
>   | 
>   | Written by Tom Tromey
>   | 
>   | and Alexandre Duret-Lutz .
>   | 
>   | AUTOV is 1.14
>   | 
>   | NOTE: Executing ACLOCAL="aclocal
> 
> --system-acdir=/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky
> -linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/aclocal-copy/
> --automake-acdir=/home/lachlan/poky/build-atmel/tmp/sysroots/x86_64-linux/u
> sr/share/aclocal-1.14" autoreconf --verbose --install --force
> --exclude=autopoint -I
> /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
> gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/
>   | autoreconf: Entering directory `'
>   | 
>   | autoreconf: configure.ac: not using Gettext
>   | 
>   | autoreconf: running: aclocal
> 
> --system-acdir=/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky
> -linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/aclocal-copy/
> --automake-acdir=/home/lachlan/poky/build-atmel/tmp/sysroots/x86_64-linux/u
> sr/share/aclocal-1.14 -I
> /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
> gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/ -I
> /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
> gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/ --force -I m4 -I
> common/m4
> 
>   | autoreconf: configure.ac: tracing
>   | 
>   | autoreconf: running: libtoolize --copy --force
>   | 
>   | libtoolize: putting auxiliary files in `.'.
>   | 
>   | libtoolize: copying file `./ltmain.sh'
>   | 
>   | libtoolize: putting macros in `m4'.
>   | 
>   | libtoolize: copying file `m4/libtool.m4'
>   | 
>   | libtoolize: copying file `m4/ltoptions.m4'
>   | 
>   | libtoolize: copying file `m4/ltsugar.m4'
>   | 
>   | libtoolize: copying file `m4/ltversion.

Re: [yocto] Layer Priority with Wildcard .bbappend Files

[Paul Eggleton]

Hi Bob / Nick,

On Monday 24 November 2014 16:25:58 Bob Cochran wrote:
> On 11/24/2014 03:22 PM, Stevens, Nick wrote:
> > I think I've encountered a bug with how multiple bbappend files are
> > processed when one of the bbappends contains a filename wildcard, but I
> > want to make sure there's not something I'm missing before filing a bug
> > report.> 
> > I have a BSP layer and a customization layer that are based on the OE/poky
> > Daisy release. The output of `bitbake-layers show-layers` looks like:
> >  layer path priority
> >  =
> >  meta  poky/meta5
> >  meta-yoctopoky/meta-yocto  5
> >  meta-yocto-bsppoky/meta-yocto-bsp  5
> >  ...ellided...
> >  meta-bsp  meta-bsp 6
> >  meta-custom   meta-custom  8
> > 
> > In meta-bsp there is a bbappend for base-files named base-
> > files_3.0.14.bbappend. The meta-bsp bbappend adds a sysctl.conf to /etc -
> > pretty straightforward:
> >  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> >  SRC_URI += "file://sysctl.conf"
> >  do_install_append() {
> >  
> >  install -m 0644 ${WORKDIR}/sysctl.conf ${D}${sysconfdir}/
> >  
> >  }
> > 
> > Now what I want to do is add a file called base-files_%.bbappend to meta-
> > custom. It has its own version of sysctl.conf, and the recipe looks like
> > this:
> >  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> > 
> > Here's where things get weird. If I run `bitbake -e base-files` and pull
> > out the section for FILESEXTRAPATHS, this is what I get (note that I've
> > stripped out the huge absolute paths to make this easier to read):
> >  # $FILESEXTRAPATHS [5 operations]
> >  #   set poky/meta/conf/documentation.conf:172
> >  # [doc] "Extends the search path the OpenEmbedded build system
> >  uses when looking for files and patches as it processes recipes and
> >  append files." #   _prepend
> >  meta-custom/recipes-core/base-files/base-files_%.bbappend:6 #
> >  "meta-custom/recipes-core/base-files/base-files:"
> >  #   _prepend
> >  meta-bsp/recipes-core/base-files/base-files_3.0.14.bbappend:3
> >  # "meta-bsp/recipes-core/base-files/base-files:"
> >  #   set data_smart.py:432 [finalize]
> >  # "meta-custom/recipes-core/base-files/base-files:"
> >  #   set data_smart.py:432 [finalize]
> >  #
> >  "meta-bsp/recipes-core/base-files/base-files:meta-custom/recipes-cor
> >  e/base-files/base-files:" # computed:
> >  #  
> >  "meta-bsp/recipes-core/base-files/base-files:meta-custom/recipes-cor
> >  e/base-files/base-files:"
> >  FILESEXTRAPATHS="meta-bsp/recipes-core/base-files/base-files:meta-cu
> >  stom/recipes-core/base-files/base-files:"> 
> > For some reason meta-bsp is coming before meta-custom in FILESEXTRAPATHS,
> > even though meta-custom has a higher priority!
>
> I also have some questions about how FILESEXTRAPATHS is supposed to work
> with append files and layer priorities.
> 
> Does a higher layer priority mean that the FILESEXTRAPATHS operation
> should occur first?  

No. bbappends are parsed in ascending layer priority order. It wouldn't make 
sense to do it in the reverse - you want the higher priority layer's settings 
to take precedence

> If this is the case, then a lower priority layer prepend will appear to the
> left of the higher layer prepend since it runs later, and this will probably
> not provide the result you want.

The highest priority layer's bbappend will prepend last, thus anything it 
prepends will be first in the list.

> The prepend and layer logic seems messy to me.  I would like to have a
> way to write my custom layer and specify that what I include in my
> SRC_URI in each recipe is definitive and can not be overwritten.
> Suggestions on how to best accomplish this will be greatly appreciated.

I think this is pretty much already the case. Is the problem that you can't 
follow the current behaviour, or that you don't completely trust the layers 
you are pulling in?
 
> I have been trying to accomplish this with FILESOVERRIDES, but this
> logic seems counterintuitive since  DISTROOVERRIDES take precedence over
> MACHINEOVERRIDES in building the file search path during the unpack task.
> 
> It seems to me that the file search path should be built using
> FILESOVERRIDES from left to right:  TRANSLATED_TARGET_ARCH,
> MACHINEOVERRIDES, and then DISTROOVERRIDES (specific to generic), but
> this isn't what I'm seeing.  Still investigating how it's all put
> together...
> 
> 
> I verified this by building an image - the sysctl.conf that ends up in
> the final image is the one from meta-bsp, not the one from meta-custom.
> But if I switch the name of base-files_%.bbappend in meta-custom to
> base-files_3.0.14.bbappend, this is what I get:
> >  # $FILE

Re: [yocto] [bitbake-devel] how to update a package on yocto project

[Paul Eggleton]

Hi Nishanth,

On Monday 24 November 2014 11:34:17 Nishanth S wrote:
> board : Intel Galileo Gen 1
> 
> I use yocto project for build image/tarball for the board.
> 
> How to update a existing package???
> 
> I mean, I use openjdk-6 on my board.
> 
> But I need to change it to openjdk-7.
> 
> I edited local.conf by adding following line.
> 
> preferred_version_openjdk = 
> 
> 
> 
> 
> I tried this but the resulting image.tar had only openjdk-6.
> 
> How do I include openjdk-7 with core-image???

There needs to be a recipe to actually provide that - PREFERRED_VERSION only 
selects between available versioned recipes. Is there an openjdk-7 recipe in 
your configuration? If not, you will need to add one.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Progress Bar

[Paul Eggleton]

Hi Mahdi,

On Saturday 22 November 2014 11:11:16 Mahdi Saadat wrote:
> ] build the image-minimal , and want to add the dialog installer for it with
> progress bar and dialog , when i use install.sh, in the image installation
> on target device the message shows that "dialog and progress could not
> find".
> could you please inform me about the creating progress bar when installing
> th image on dest device

Sorry, I don't understand the question because there isn't enough detail. I'm 
not even sure which part of the system you're using. Which install.sh is this? 
"dialog and progress could not find" - is this exactly how the error message is 
written?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New error in 1.7

[peterengcomau001]

 
 the change to oprofile.inc and the associated patch appear to be
already present in the meta data.
Any other ideas what could be causing the problem?
Lachlan

- Original Message -
 From: "Paul Eggleton" .eggle...@linux.intel.com> 
To:
Cc:
Sent:Tue, 25 Nov 2014 10:09:47 +
Subject:Re: [yocto] New error in 1.7

 Hi there,

 On Tuesday 25 November 2014 19:27:13 peterengcomau...@adam.com.au
wrote:
 > thank you. i have fixed the curl problem but a new problem has
occured
 > with the build. This problem did not appear in v1.6.1. The problem
is:
 > 
 > lachlan@lachlan-SVP13215PXB:~/poky/build-atmel$ bitbake
 > atmel-qt5-demo-image -c populate_sdk
 > 
 > Loading cache: 100%
 > 
 >
|###
 >
|###
 > |#|
 > ETA: 00:00:00
 > 
 > Loaded 2108 entries from dependency cache.
 > 
 > NOTE: Resolving any missing task queue dependencies
 > 
 > Build Configuration:
 > 
 > BB_VERSION = "1.24.0"
 > 
 > BUILD_SYS = "x86_64-linux"
 > 
 > NATIVELSBSTRING = "Ubuntu-14.04"
 > 
 > TARGET_SYS = "arm-poky-linux-gnueabi"
 > 
 > MACHINE = "sama5d3xek"
 > 
 > DISTRO = "poky"
 > 
 > DISTRO_VERSION = "1.7"
 > 
 > TUNE_FEATURES = "arm armv7a vfp thumb callconvention-hard
cortexa5"
 > 
 > 
 > TARGET_FPU = "vfp"
 > 
 > meta-atmel = "my_branch:711809b0d91f816b10e70508986b3f43098000ba"
 > 
 > meta-qt5 = "my_branch:0732e184acef5e0200f46d7f95702774e5de1904"
 > 
 > meta
 > 
 > meta-yocto
 > 
 > meta-yocto-bsp = "dizzy:db7f4f31c915a59c502cac4be905d23df5246b3d"
 > 
 > meta-oe
 > 
 > meta-python
 > 
 > meta-networking
 > 
 > meta-ruby = "my_branch:9efaed99125b1c4324663d9a1b2d3319c74e7278"
 > 
 > NOTE: Preparing runqueue
 > 
 > NOTE: Executing SetScene Tasks
 > 
 > NOTE: Executing RunQueue Tasks
 > 
 > ERROR: Function failed: do_configure (log file is located at
 >
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
 > gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_configure.5736)
 > 
 > 
 > ERROR: Logfile of failure stored in:
 >
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
 > gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_configure.5736
 > Log data follows:
 > | DEBUG: Executing python function sysroot_cleansstate
 > | 
 > | DEBUG: Python function sysroot_cleansstate finished
 > | 
 > | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
 > 
 > 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
 > 'common']
 > 
 > | DEBUG: Executing shell function autotools_preconfigure
 > | 
 > | DEBUG: Shell function autotools_preconfigure finished
 > | 
 > | DEBUG: Executing python function autotools_copy_aclocals
 > | 
 > | DEBUG: Python function autotools_copy_aclocals finished
 > | 
 > | DEBUG: Executing shell function do_configure
 > | 
 > | automake (GNU automake) 1.14.1
 > | 
 > | Copyright (C) 2013 Free Software Foundation, Inc.
 > | 
 > | License GPLv2+: GNU GPL version 2 or later
 > | 
 > | This is free software: you are free to change and redistribute
it.
 > | 
 > | 
 > | There is NO WARRANTY, to the extent permitted by law.
 > | 
 > | 
 > | 
 > | Written by Tom Tromey
 > | 
 > | and Alexandre Duret-Lutz .
 > | 
 > | AUTOV is 1.14
 > | 
 > | NOTE: Executing ACLOCAL="aclocal
 > 
 >
--system-acdir=/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky
 >
-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/aclocal-copy/
 >
--automake-acdir=/home/lachlan/poky/build-atmel/tmp/sysroots/x86_64-linux/u
 > sr/share/aclocal-1.14" autoreconf --verbose --install --force
 > --exclude=autopoint -I
 >
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
 > gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/
 > | autoreconf: Entering directory `'
 > | 
 > | autoreconf: configure.ac: not using Gettext
 > | 
 > | autoreconf: running: aclocal
 > 
 >
--system-acdir=/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky
 >
-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/aclocal-copy/
 >
--automake-acdir=/home/lachlan/poky/build-atmel/tmp/sysroots/x86_64-linux/u
 > sr/share/aclocal-1.14 -I
 >
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
 > gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/ -I
 >
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/
 > gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/m4/ --force
-I m4 -I
 > common/m4
 > 
 > | autoreconf: configure.ac: tracing
 > | 
 > | autoreconf: running: libtoolize --copy --force
 > | 
 > | libtoolize: putting auxiliary files in `.'.
 > | 
 > | libtoolize: copying file `./ltmain.sh'
 > | 
 > | libtoolize: putting macros in `m4'.
 > | 
 > | libtoolize: copying file `m4/libtool.m4'
 > | 
 > | libtoolize: copying file `m4/ltoptions.m4'
 > | 
 > | libtoolize: copying file `m4/ltsugar.m4'
 > | 
 > | libtoolize: copying file `m4/ltversion.m4'
 > | 
 > | libtoolize: c

Re: [yocto] New error in 1.7

[Paul Eggleton]

On Tuesday 25 November 2014 22:08:41 peterengcomau...@adam.com.au wrote:
> > > | Makefile.am: error: required file './AUTHORS' not found
> > 
> > This is likely a result of the --foreign option being removed - see:
> > 
> > http://www.yoctoproject.org/docs/1.7/ref-manual/ref-> > 
> > manual.html#migration-1.7-autotools-class-changes
>
>  the change to oprofile.inc and the associated patch appear to be
> already present in the meta data.
> Any other ideas what could be causing the problem?

The patch to oprofile is just an example of what you need to do to solve this 
type of issue - you need to make a similar change to the failing recipe 
(gstreamer1.0-plugins-hantro in this instance).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Progress Bar

[Paul Eggleton]

On Tuesday 25 November 2014 15:26:46 Mahdi Saadat wrote:
> > On Saturday 22 November 2014 11:11:16 Mahdi Saadat wrote:
> > > ] build the image-minimal , and want to add the dialog installer for
> > > it with progress bar and dialog , when i use install.sh, in the image
> > > installation on target device the message shows that "dialog and
> > > progress could not find".
> > > could you please inform me about the creating progress bar when
> > > installing th image on dest device
> 
> > Sorry, I don't understand the question because there isn't enough detail.
> > I'm not even sure which part of the system you're using. Which install.sh
> > is this? "dialog and progress could not find" - is this exactly how the
> > error message is written?
>
> The problem is as below:
> I want to add installation progress bar on my final image, so when I going
> to install on the target machine it shows the progress bar of installing the
> image and copying the files.
> I edit the init.install.sh file in the meta folder and add "dialog command
> or PV command" to it, but when I installing  the image on the target machine
> it says no "dialog command or PV command" found.
> 
> Is it an approach to create progress bar when installing image on target
> machine?

This is functionality we don't currently provide as far as I know, and there 
are lots of different ways you could implement it. If you need additional 
packages to support this behaviour you'll need to ensure they get installed 
into the initramfs; by default, that would be determined in the 
core-image-minimal-initramfs recipe - you can either modify that (for testing) 
or preferably copy it and then specify your alternative initramfs image recipe 
by setting INITRD_IMAGE to point to its name.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [bitbake-devel] how to update a package on yocto project

[Iorga, Cristian]

Hi,
Nishanth, I am assuming you are using the meta-java layer, right?
If so, have you tried my suggestions?
/Cristian


-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Paul Eggleton
Sent: Tuesday, November 25, 2014 1:20 PM
To: Nishanth S
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [bitbake-devel] how to update a package on yocto project

Hi Nishanth,

On Monday 24 November 2014 11:34:17 Nishanth S wrote:
> board : Intel Galileo Gen 1
> 
> I use yocto project for build image/tarball for the board.
> 
> How to update a existing package???
> 
> I mean, I use openjdk-6 on my board.
> 
> But I need to change it to openjdk-7.
> 
> I edited local.conf by adding following line.
> 
> preferred_version_openjdk = 
> 
> 
> 
> 
> I tried this but the resulting image.tar had only openjdk-6.
> 
> How do I include openjdk-7 with core-image???

There needs to be a recipe to actually provide that - PREFERRED_VERSION only 
selects between available versioned recipes. Is there an openjdk-7 recipe in 
your configuration? If not, you will need to add one.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New error in 1.7

[peterengcomau001]

This is new territory for me.

I have created the following patch
diff --git a/configure.ac b/configure.ac
--- a/configure.ac
+++ b/configure.ac
@@ -16 +16 @@ AC_CONFIG_SRCDIR([libop/op_config.h])
-AM_INIT_AUTOMAKE
+AM_INIT_AUTOMAKE([foreign])

but i get the error

ERROR: Command Error: exit status: 1  Output:
Applying patch automake-foreign.patch
patching file configure.ac
Hunk #1 FAILED at 16.
1 out of 1 hunk FAILED -- rejects in file configure.ac
Patch automake-foreign.patch does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch
ERROR: Logfile of failure stored in:
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_patch.15332
ERROR: Task 598
(/home/lachlan/poky/meta-atmel/recipes-multimedia/gstreamer1.0-plugins/gstreamer1.0-plugins-hantro_1.0.bb,
do_patch) failed with exit code '1'

if I delete the  @@ line I get the following error.

 ERROR: Command Error: exit status: 1  Output:
Applying patch automake-foreign.patch
patch:  Only garbage was found in the patch input.
Patch automake-foreign.patch does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch
ERROR: Logfile of failure stored in:
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_patch.16828
ERROR: Task 598
(/home/lachlan/poky/meta-atmel/recipes-multimedia/gstreamer1.0-plugins/gstreamer1.0-plugins-hantro_1.0.bb,
do_patch) failed with exit code '1'

Can you direct me to some information that describes the exact syntax
for creating patches?
Thanks
Lachlan

- Original Message -
From: "Paul Eggleton" 
To:
Cc:
Sent:Tue, 25 Nov 2014 11:43:50 +
Subject:Re: [yocto] New error in 1.7

 On Tuesday 25 November 2014 22:08:41 peterengcomau...@adam.com.au
wrote:
 > > > | Makefile.am: error: required file './AUTHORS' not found
 > > 
 > > This is likely a result of the --foreign option being removed -
see:
 > > 
 > > http://www.yoctoproject.org/docs/1.7/ref-manual/ref-> >
manual.html#migration-1.7-autotools-class-changes
 >
 > the change to oprofile.inc and the associated patch appear to be
 > already present in the meta data.
 > Any other ideas what could be causing the problem?

 The patch to oprofile is just an example of what you need to do to
solve this 
 type of issue - you need to make a similar change to the failing
recipe 
 (gstreamer1.0-plugins-hantro in this instance).

 Cheers,
 Paul

 -- 

 Paul Eggleton
 Intel Open Source Technology Centre
 Message sent via Adam Internet WebMail - http://www.adam.com.au/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New error in 1.7

[Anders Darander]

* peterengcomau...@adam.com.au  [141125 13:44]:
>This is new territory for me.
>I have created the following patch
>diff --git a/configure.ac b/configure.ac
>--- a/configure.ac
>+++ b/configure.ac
>@@ -16 +16 @@ AC_CONFIG_SRCDIR([libop/op_config.h])
>-AM_INIT_AUTOMAKE
>+AM_INIT_AUTOMAKE([foreign])

Yep, that's not really a valid patch file (at least not one that can be
applied.

>Can you direct me to some information that describes the exact syntax
>for creating patches?

If you want to do it by hand, look at the "Creating patches with diff"
section on http://jungels.net/articles/diff-patch-ten-minutes.html.

If you think you might need to add multiple patches, rework them etc.
I'd recommend using git.

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Meta-Raspberry and Meta-Oracle-Java: ERROR

[Tran TriTin]

Hi all,

i am newbie to Yocto. Last days i tried to build an image for my
RaspberryPi with Meta-Raspberry and Meta-Oracle-Java but it did not work.
This is error i received. Can anyone help me?
Thanks in advance.






































*[tvtritin@g-105-1 build-raspberry-java]$ bitbake -k rpi-basic-imageLoading
cache: 100% |###| ETA:
00:00:00Loaded 1320 entries from dependency cache.NOTE: Resolving any
missing task queue dependenciesBuild Configuration:BB_VERSION=
"1.24.0"BUILD_SYS = "x86_64-linux"NATIVELSBSTRING   =
"CentOS-6.5"TARGET_SYS= "arm-poky-linux-gnueabi"MACHINE   =
"raspberrypi"DISTRO= "poky"DISTRO_VERSION=
"1.7"TUNE_FEATURES = "arm armv6 vfp"TARGET_FPU=
"vfp"meta  meta-yoctometa-yocto-bsp
meta-raspberrypi  =
"dizzy:db7f4f31c915a59c502cac4be905d23df5246b3d"meta-oracle-java  =
"master:d5256fe7ae592f19ffe0619c093b333eb9f92a93"NOTE: Preparing
runqueueNOTE: Executing SetScene TasksNOTE: Executing RunQueue TasksERROR:
Unable to install packages. Command
'/home/tvtritin/DemoYOCTO/poky1.7/build-raspberry-java/tmp/sysroots/x86_64-linux/usr/bin/smart
--quiet
--data-dir=/home/tvtritin/DemoYOCTO/poky1.7/build-raspberry-java/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-basic-image/1.0-r0/rootfs/var/lib/smart
install -y packagegroup-core-ssh-dropbear@all run-postinsts@all
psplash-raspberrypi@armv6_vfp kernel-modules@raspberrypi
oracle-jse-ejre-arm-vfp-hflt-client-headless@armv6_vfp
packagegroup-core-boot@raspberrypi' returned 1:error: Can't install
oracle-jse-ejre-arm-vfp-hflt-client-headless-1.7.0-u71r0@armv6_vfp: no
package provides ld-linux-armhf.so.3(GLIBC_2.4)ERROR: Function failed:
do_rootfsERROR: Logfile of failure stored in:
/home/tvtritin/DemoYOCTO/poky1.7/build-raspberry-java/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-basic-image/1.0-r0/temp/log.do_rootfs.17752ERROR:
Task 7
(/home/tvtritin/DemoYOCTO/poky1.7/meta-raspberrypi/recipes-core/images/rpi-basic-image.bb
, do_rootfs) failed with exit code '1'NOTE:
Tasks Summary: Attempted 2074 tasks of which 2073 didn't need to be rerun
and 1 failed.No currently running tasks (2073 of 2075)Summary: 1 task
failed:
/home/tvtritin/DemoYOCTO/poky1.7/meta-raspberrypi/recipes-core/images/rpi-basic-image.bb
, do_rootfsSummary: There were 2 ERROR messages
shown, returning a non-zero exit code.*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New error in 1.7

[peterengcomau001]

 My original problem is that the image built in 1.6.1 does not build
in 1.7. Paul indicated this is probably because of the -foreign issue
as referred to in the reference manual Section 5.6.3 when upgrading. 
What I need to do is modify my recipe to include this. I understand
once I have modified the recipe I can generate a patch against the
original.
However, I still cannot identify the original change to the recipe
required to add this item.
I have added to the recipe
EXTRA_OECONF = " 'AM_INIT_AUTOMAKE([foreign]); "
Is this the correct change to the recipe to ensure the config.ac file
is updated so that any non-conformance with GNU guidelines is
overlooked?
I am still getting the original error error.
Do I need to add :do_config() {}and if so, what do I put in the
between the brackets? note that it looks like do_config is being run
already because that is what is generating the error
RegardsLachlan 

- Original Message -
From: "Anders Darander" 
To:"peterengcomau...@adam.com.au" 
Cc:"Paul Eggleton" , "yocto@yoctoproject.org" 
Sent:Tue, 25 Nov 2014 13:56:41 +0100
Subject:Re: [yocto] New error in 1.7

 * peterengcomau...@adam.com.au  [141125 13:44]:
 > This is new territory for me.
 > I have created the following patch
 > diff --git a/configure.ac b/configure.ac
 > --- a/configure.ac
 > +++ b/configure.ac
 > @@ -16 +16 @@ AC_CONFIG_SRCDIR([libop/op_config.h])
 > -AM_INIT_AUTOMAKE
 > +AM_INIT_AUTOMAKE([foreign])

 Yep, that's not really a valid patch file (at least not one that can
be
 applied.

 > Can you direct me to some information that describes the exact
syntax
 > for creating patches?

 If you want to do it by hand, look at the "Creating patches with
diff"
 section on http://jungels.net/articles/diff-patch-ten-minutes.html.

 If you think you might need to add multiple patches, rework them
etc.
 I'd recommend using git.

 Cheers,
 Anders

 -- 
 Anders Darander
 ChargeStorm AB / eStorm AB
 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
 Message sent via Adam Internet WebMail - http://www.adam.com.au/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Layer Priority with Wildcard .bbappend Files

[Stevens, Nick]

Hi Paul,

> > I verified this by building an image - the sysctl.conf that ends up in
> > the final image is the one from meta-bsp, not the one from meta-custom.
> > But if I switch the name of base-files_%.bbappend in meta-custom to
> > base-files_3.0.14.bbappend, this is what I get:
> > >  # $FILESEXTRAPATHS [5 operations]
> > >  #   set poky/meta/conf/documentation.conf:172
> > >  # [doc] "Extends the search path the OpenEmbedded build
> system
> > >  uses when looking for files and patches as it processes recipes
> and
> > >  append files." #   _prepend
> > >  meta-bsp/recipes-core/base-files/base-files_3.0.14.bbappend:3 #
> > >  "meta-bsp/recipes-core/base-files/base-files:"
> > >  #   _prepend
> > >  meta-custom/recipes-core/base-files/base-files_3.0.14.bbappend:6
> #
> > >"meta-custom/recipes-core/base-files/base-files:"
> > >  #   set data_smart.py:432 [finalize]
> > >  # "meta-bsp/recipes-core/base-files/base-files:"
> > >  #   set data_smart.py:432 [finalize]
> > >  #
> > >  "meta-custom/recipes-core/base-files/base-files:meta-bsp/recipes-
> cor
> > >  e/base-files/base-files:" # computed:
> > >  #
> > >  "meta-custom/recipes-core/base-files/base-files:meta-bsp/recipes-
> cor
> > >  e/base-files/base-files:"
> > >  FILESEXTRAPATHS="meta-custom/recipes-core/base-files/base-
> files:meta
> > >  -bsp/recipes-core/base-files/base-files:">
> > > And now the sysctl.conf file is being pulled from meta-custom.
> 
> That absolutely should not happen. If you change it back does it revert to
> the version from meta-bsp? The wildcarding should not change the order in
> which the files are applied. The only corner case I can think of would be
> if the layer priority values are the same number - this isn't the case is
> it?

The behavior does reappear if I change the file name back to a wildcard. And 
no, the layers are different priorities - meta-custom is priority 8 and 
meta-bsp is priority 6.

Definitely sounds like there's some unexpected behavior here. I am going to dig 
in some more and see if I can find a limited test case that reproduces the 
issue, and then I'll get a bug report opened.

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

Re: [yocto] New error in 1.7

[Anders Darander]

On 25 November 2014 17:13:17 CET, "peterengcomau...@adam.com.au" 
 wrote:
>My original problem is that the image built in 1.6.1 does not build in
>1.7. Paul indicated this is probably because of the -foreign issue as
>referred to in the reference manual Section 5.6.3 when upgrading. 
>
>
>What I need to do is modify my recipe to include this. I understand
>once I have modified the recipe I can generate a patch against the
>original.

The easiest way is likely to patch configure.ac, similar to what was done in 
http://git.openembedded.org/openembedded-core/commit/?id=60da074fea280d8190e7439361712dcc86177f12

So you were on the right track in your earlier email. 

>However, I still cannot identify the original change to the recipe
>required to add this item.
>
>
>I have added to the recipe
>
>
>EXTRA_OECONF = " 'AM_INIT_AUTOMAKE([foreign]); "
>
>
>Is this the correct change to the recipe to ensure the config.ac file
>is updated so that any non-conformance with GNU guidelines is
>overlooked?

No, what that line does is add some extra argument to the call to configure. 
AM_INIT_AUTOMAKE is a macro in configure.ac. 

 Create the patch that you talked about in got previous email, and make sure 
that it applies. Then this problem will go away. 

Cheers, 
Anders 

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

Re: [yocto] Layer Priority with Wildcard .bbappend Files

[Bob Cochran]

On 11/25/2014 06:12 AM, Paul Eggleton wrote:

Hi Bob / Nick,

On Monday 24 November 2014 16:25:58 Bob Cochran wrote:

On 11/24/2014 03:22 PM, Stevens, Nick wrote:

I think I've encountered a bug with how multiple bbappend files are
processed when one of the bbappends contains a filename wildcard, but I
want to make sure there's not something I'm missing before filing a bug
report.>
I have a BSP layer and a customization layer that are based on the OE/poky
Daisy release. The output of `bitbake-layers show-layers` looks like:
  layer path priority
  =
  meta  poky/meta5
  meta-yoctopoky/meta-yocto  5
  meta-yocto-bsppoky/meta-yocto-bsp  5
  ...ellided...
  meta-bsp  meta-bsp 6
  meta-custom   meta-custom  8

In meta-bsp there is a bbappend for base-files named base-
files_3.0.14.bbappend. The meta-bsp bbappend adds a sysctl.conf to /etc -
pretty straightforward:
  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
  SRC_URI += "file://sysctl.conf"
  do_install_append() {

  install -m 0644 ${WORKDIR}/sysctl.conf ${D}${sysconfdir}/

  }

Now what I want to do is add a file called base-files_%.bbappend to meta-
custom. It has its own version of sysctl.conf, and the recipe looks like
this:
  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

Here's where things get weird. If I run `bitbake -e base-files` and pull
out the section for FILESEXTRAPATHS, this is what I get (note that I've
stripped out the huge absolute paths to make this easier to read):
  # $FILESEXTRAPATHS [5 operations]
  #   set poky/meta/conf/documentation.conf:172
  # [doc] "Extends the search path the OpenEmbedded build system
  uses when looking for files and patches as it processes recipes and
  append files." #   _prepend
  meta-custom/recipes-core/base-files/base-files_%.bbappend:6 #
  "meta-custom/recipes-core/base-files/base-files:"
  #   _prepend
  meta-bsp/recipes-core/base-files/base-files_3.0.14.bbappend:3
  # "meta-bsp/recipes-core/base-files/base-files:"
  #   set data_smart.py:432 [finalize]
  # "meta-custom/recipes-core/base-files/base-files:"
  #   set data_smart.py:432 [finalize]
  #
  "meta-bsp/recipes-core/base-files/base-files:meta-custom/recipes-cor
  e/base-files/base-files:" # computed:
  #
  "meta-bsp/recipes-core/base-files/base-files:meta-custom/recipes-cor
  e/base-files/base-files:"
  FILESEXTRAPATHS="meta-bsp/recipes-core/base-files/base-files:meta-cu
  stom/recipes-core/base-files/base-files:">
For some reason meta-bsp is coming before meta-custom in FILESEXTRAPATHS,
even though meta-custom has a higher priority!


I also have some questions about how FILESEXTRAPATHS is supposed to work
with append files and layer priorities.

Does a higher layer priority mean that the FILESEXTRAPATHS operation
should occur first?


No. bbappends are parsed in ascending layer priority order. It wouldn't make
sense to do it in the reverse - you want the higher priority layer's settings
to take precedence


If this is the case, then a lower priority layer prepend will appear to the
left of the higher layer prepend since it runs later, and this will probably
not provide the result you want.


The highest priority layer's bbappend will prepend last, thus anything it
prepends will be first in the list.


The prepend and layer logic seems messy to me.  I would like to have a
way to write my custom layer and specify that what I include in my
SRC_URI in each recipe is definitive and can not be overwritten.
Suggestions on how to best accomplish this will be greatly appreciated.


I think this is pretty much already the case. Is the problem that you can't
follow the current behaviour, or that you don't completely trust the layers
you are pulling in?



Thanks Paul.  Something is amiss when I try to prepend my recipes. I 
suspect it has something to do with OVERRIDE interactions.I'm 
digging and will report later.







I have been trying to accomplish this with FILESOVERRIDES, but this
logic seems counterintuitive since  DISTROOVERRIDES take precedence over
MACHINEOVERRIDES in building the file search path during the unpack task.

It seems to me that the file search path should be built using
FILESOVERRIDES from left to right:  TRANSLATED_TARGET_ARCH,
MACHINEOVERRIDES, and then DISTROOVERRIDES (specific to generic), but
this isn't what I'm seeing.  Still investigating how it's all put
together...


I verified this by building an image - the sysctl.conf that ends up in
the final image is the one from meta-bsp, not the one from meta-custom.
But if I switch the name of base-files_%.bbappend in meta-custom to
base-files_3.0.14.bbappend, this is what I get:

  # $FILESEXTRAPATHS [5 operations]
  #   set poky/meta

[yocto] Headers missing in generated SDK

[Syed Moosvi]

Hi All,

   I am working on danny branch and having an issue with respect to
adding headers in the generated SDK toolchain.

I am generating the SDK using

$ bitbake -c populate_sdk image_name

When I generate the SDK, the openssl and alsa headers were missing from
/opt/poky/1.3/sysroots/image-poky-linux-gnueabi/usr/include

Adding the following did add the ALSA headers but the openssl headers are
still missing

TOOLCHAIN_TARGET_TASK_append = " openssl-dev"

TOOLCHAIN_TARGET_TASK_append = " alsa-dev"

Therefore can anyone please let me know the following

1) What headers ar populated in /opt/poky/1.3/sysroots/image
-poky-linux-gnueabi/usr/include.

2) How do I make the openssl headers appear in /opt/poky/1.3/sysroots/image
-poky-linux-gnueabi/usr/include

3) I though all the headers for all the libs used in target will be
populated in the SDK. Is this not true?

4) Also noticed the headers are present in but not in generated SDK.
/tmp/sysroots/image/usr/include/openssl/


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

Re: [yocto] New error in 1.7

[peterengcomau001]

Thanks for your patience. I was successful in building the patch as
follows:
__
--- a/configure.ac    2014-08-28 03:20:36.0 +0300
+++ b/configure.ac    2014-11-25 23:22:45.129711196 +0300
@@ -13,7 +13,7 @@
 AG_GST_INIT
 
 dnl initialize automake
-AM_INIT_AUTOMAKE([-Wno-portability 1.11 no-dist-gzip dist-xz
tar-ustar])
+AM_INIT_AUTOMAKE([-Wno-portability 1.11 no-dist-gzip dist-xz
tar-ustar foreign])
 
 dnl define PACKAGE_VERSION_* variables
 AS_VERSION 
 
build proceeds past do_config but now fails at do_complie for the
same module.

The last part of the error is as follows:
__
| In file included from
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/gst-libs/ext/g1/dwl/gstdwlallocator.c:31:0:
|
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/gst-libs/ext/g1/dwl/gstdwlallocator.h:36:28:
fatal error: gstg1allocator.h: No such file or directory
|  #include "gstg1allocator.h"
| ^
| compilation terminated.
| make[5]: *** [libgstdwlallocator_1.0_la-gstdwlallocator.lo] Error 1
| make[5]: Leaving directory
`/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs/ext/g1/dwl'
| make[4]: *** [all-recursive] Error 1
| make[4]: Leaving directory
`/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs/ext/g1'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory
`/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs/ext'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory
`/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory
`/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/build'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_compile.3977)
ERROR: Task 603
(/home/lachlan/poky/meta-atmel/recipes-multimedia/gstreamer1.0-plugins/gstreamer1.0-plugins-hantro_10.bb,
do_compile) failed with exit code '1'
_

Any ides on how to proceed?
Maybe i go back to using poky 1.6.1 ?

Thanks for any ideas
Lachlan

 

- Original Message -
From: "Anders Darander" 
To:"peterengcomau...@adam.com.au" 
Cc:"yocto@yoctoproject.org" 
Sent:Tue, 25 Nov 2014 19:19:27 +0100
Subject:Re: [yocto] New error in 1.7

 On 25 November 2014 17:13:17 CET, "peterengcomau...@adam.com.au" 
wrote:
 >My original problem is that the image built in 1.6.1 does not build
in
 >1.7. Paul indicated this is probably because of the -foreign issue
as
 >referred to in the reference manual Section 5.6.3 when upgrading. 
 >
 >
 >What I need to do is modify my recipe to include this. I understand
 >once I have modified the recipe I can generate a patch against the
 >original.

 The easiest way is likely to patch configure.ac, similar to what was
done in
http://git.openembedded.org/openembedded-core/commit/?id=60da074fea280d8190e7439361712dcc86177f12

 So you were on the right track in your earlier email. 

 >However, I still cannot identify the original change to the recipe
 >required to add this item.
 >
 >
 >I have added to the recipe
 >
 >
 >EXTRA_OECONF = " 'AM_INIT_AUTOMAKE([foreign]); "
 >
 >
 >Is this the correct change to the recipe to ensure the config.ac
file
 >is updated so that any non-conformance with GNU guidelines is
 >overlooked?

 No, what that line does is add some extra argument to the call to
configure. AM_INIT_AUTOMAKE is a macro in configure.ac. 

 Create the patch that you talked about in got previous email, and
make sure that it applies. Then this problem will go away. 

 Cheers, 
 Anders 

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

 Message sent via Adam Internet WebMail - http://www.adam.com.au/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Release Candidate Build for yocto-1.5.4.rc1 now available.

[Poky Build User]

A release candidate build for yocto-1.5.4.rc1 is now available at:

 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.5.4.rc1


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : b62c8e3f27811183dafec935b3ae3193f66df3fe 
meta-fsl-arm : 5fdb620c09df11e70434092f675c891e0ba84108 
meta-minnow : 9aa60d0eaf03fe30670acf581eaf7e57c76b5f99 
meta-qt3 : 4772424ab69908d4e3b9d6d4717ca889468e6acd 
meta-fsl-ppc : 40465bac88ca28b554cff35346341d19552548bf 
poky : de14d21bc6633ddeb810cef051b91ee322276496 


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] how to separate packages in downloads folder into those that run on target and those that do not run on target?

[Gangadhar N]

Hi All,
I want to separate the packages in downloads folder. I want to separate the
packages into those that run on target and those that do not run on the
target. The idea is to feed the packages that go into target to fossology
tool to get licence of each and every file. I know that the Yocto Project
generates a license manifest during image creation that is located in
${DEPLOY_DIR}/licenses/*image_name-datestamp* to assist with any audits.
But we need to use fossology. Please suggest a method/command and guide me.

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

Re: [yocto] how to separate packages in downloads folder into those that run on target and those that do not run on target?

[Wolfgang Denk]

Dear Gangadhar,

In message  
you wrote:
> 
> I want to separate the packages in downloads folder. I want to separate the
> packages into those that run on target and those that do not run on the
> target. The idea is to feed the packages that go into target to fossology


Do you think such a separation is possible at all?  Depending on your
target configuration, packages might go into both - for example, if
you build SDK / toolchain images, then gcc and related tools will be
both in the cross tools and in the target file system.

And why do you need to split the downloads folder for that?  You have
the list of packages that get installed into your target file system -
is this not sufficient?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
The complexity of software is an essential property, not an  acciden-
tal  one. Hence, descriptions of a software entity that abstract away
its complexity often abstract away its essence.- Fred Brooks, Jr.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Support for writable files with a read-only root file system

[Matt Schuckmann]

I've been investigating the support for read only root file systems and trying 
to suss out how to support persistent writeable files in my image where the 
root file system is read only, this seems like a very common thing for an 
embedded Linux system to need but I'm not seeing the support for it. 
 
I should note that I'm working off of the Dylan branch, I'm not sure if things 
have changed in a newer branch. 

So far I've had to read the code to figure out as much as I have, and I haven't 
found any documentation for this, am I missing something? 

It appears that my recipe(s) are supposed to install a volatiles file under 
${D}${sysconfdir}/default/volatiles/ that lists out the volatile directories, 
links and files that need to be created in the image. 

For writeable persistent files I would presume that I should specify links that 
point to some place on a write partition. 

What I don't see is any sort of mechanism for setting up the default files on 
that writeable partition, am I on my own for this or is there some other 
recommended mechanism. 

In my early research I found the MentorEmbedded/meta-ro-rootfs layer that had a 
nifty way of specifying VOLATILE_BINDS to create a list of binds that should 
occur at boot up and in the process creating the mounts if the target of the 
bind didn't exist a copy was made from the read only location, this appears to 
have provided a sort of default to go into the writeable location. Was this 
functionality abandoned when support for ro-rootfs was brought into oe-core? If 
so why? 

A good example for the kind of writeable persistent file that I intend to have 
is /etc/network/interfaces
How do I go about letting the init_ifupdown recipe install it normally and then 
have another recipe or even the image configure it to be either a link or a 
bind mount at another location while still preserving the default contents. 

I hope I'm making sense here. 

Thanks,
Matt S. 

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