Re: [yocto] Simple recipe quit working in dizzy

[Paul Eggleton]

Hi Jim,

On Wednesday 18 February 2015 20:33:43 Jim Rafert wrote:
> The following recipe, spectra-postbuild_0.1.bb, quit working when I ported
> from 1.6 daisy to 1.7.1 dizzy.  I include the recipe in my image by adding
> it at the end of of the IMAGE_INSTALL_append variable in my local.conf
> file.  The purpose of the recipe is simply to lay down some files that will
> later be used by an installer script.  Two if the files are deposited in
> the root directory, and the rest are placed in the /install/spectra
> directory, which is created by the recipe.  Nothing is compiled or
> transformed in any way.
> 
> When I bitbake the recipe, then bitbake core-image-full-cmdline, both
> complete without errors. When I look at the contents of the rpm file
> produced by the recipe, all the files and directories are listed. However,
> when I examine the file system images created, only the two files that I
> place in the root directory (/) are there, and the entire /install
> directory hierarchy is missing. If I modify the recipe such that the
> missing files are placed in a directory that is already created by other
> recipes (/home/root), all the files are deposited as expected.
> 
> I have looked at section 5.6 of the Yocto reference manual, "Moving to the
> Yocto Project 1.7 Release", but did not see anything that was obviously
> relevant.
> 
> Can someone tell me how to fix this for dizzy?
> 
> ##
> # spectra-postbuild_0.1.bb
> ##
> 
> SUMMARY = "Post processing of configuration files for SpectraOS"
> SECTION = "base"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
> "file://${WORKDIR}/COPYRIGHT;md5=349c872e0066155e1818b786938876a4" 
> PR = "r0"
> 
> SRC_URI = "file://inittab \
>file://fstab \
>file://rsyslog.conf \
>file://profile \
>file://grub.cfg \
>file://mount.sh \
>file://RELEASE-NOTES.txt \
>file://Spectra-OS-Version \
>file://initializeCustomKernelModules \
>file://firewall \
>file://sysctl.conf \
>file://InstallOS.sh \
>file://COPYRIGHT \
>file://WinCE_LCM.tar.bz \
>"
> 
> FILES_${PN} =  "/RELEASE-NOTES.txt \
> /Spectra-OS-Version \
> /install \
> /install/spectra \
> /install/spectra/InstallOS.sh \
> /install/spectra/fstab \
> /install/spectra/mount.sh \
> /install/spectra/grub.cfg \
> /install/spectra/rsyslog.conf \
> /install/spectra/profile \
> /install/spectra/inittab \
> /install/spectra/WinCE_LCM.tar.bz \
> /install/spectra/sysctl.conf \
> /install/spectra/init.d \
> /install/spectra/rc5.d \
> /install/spectra/init.d/initializeCustomKernelModules \
> /install/spectra/init.d/firewall \
> "
> 
> do_install () {
> install -m 755 ${WORKDIR}/RELEASE-NOTES.txt ${D}
> install -m 755 ${WORKDIR}/Spectra-OS-Version ${D}
> install -d ${D}/install
> install -d ${D}/install/spectra
> install -m 544 ${WORKDIR}/inittab ${D}/install/spectra
> install -m 755 ${WORKDIR}/fstab ${D}/install/spectra
> install -m 755 ${WORKDIR}/rsyslog.conf ${D}/install/spectra
> install -m 755 ${WORKDIR}/profile ${D}/install/spectra
> install -m 755 ${WORKDIR}/grub.cfg ${D}/install/spectra
> install -m 755 ${WORKDIR}/mount.sh ${D}/install/spectra
> install -m 755 ${WORKDIR}/InstallOS.sh ${D}/install/spectra
> install -m 755 ${WORKDIR}/sysctl.conf ${D}/install/spectra
> install -m 644 ${WORKDIR}/WinCE_LCM.tar.bz ${D}/install/spectra
> install -m 755 ${WORKDIR}/firewall ${D}/install/spectra
> install -m 755 ${WORKDIR}/initializeCustomKernelModules
> ${D}/install/spectra
> 
> }

Hmm, so I can't see anything immediately wrong with the recipe that would lead 
to a problem such as what you describe, so rather than something expected 
change between releases this looks more like a bug. Is there anything in the 
log.do_rootfs for the image that might indicate something going wrong? Perhaps 
an uncaught error?

Cheers,
Paul

-- 

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

[yocto] [RFT] gcc 5.0 recipes available for testing

[Khem Raj]

Hi All

Encouraged by help received on testing out glibc 2.21, now  I have put together 
OE recipes for gcc-5

GCC 5.0 is in prerelease stage 4 ( open for regression and doc fixes only) 

https://gcc.gnu.org/ml/gcc/2015-01/msg00156.html

The recipes are available here

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-5.0

you just need the topmost commit and then set 

GCCVERSION = "5.0"
SDKGCCVERSION = "5.0"

in local.conf

It has been lightly tested thus far but try it out and report issues you 
observe in your build setups, we will bake it there
until 5.0 release

Thanks for helping out

-Khem

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

Re: [yocto] [RFT] gcc 5.0 recipes available for testing

[Robert P. J. Day]

On Fri, 20 Feb 2015, Khem Raj wrote:

> Hi All
>
> Encouraged by help received on testing out glibc 2.21, now  I have put 
> together OE recipes for gcc-5
>
> GCC 5.0 is in prerelease stage 4 ( open for regression and doc fixes only)
>
> https://gcc.gnu.org/ml/gcc/2015-01/msg00156.html
>
> The recipes are available here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-5.0
>
> you just need the topmost commit and then set
>
> GCCVERSION = "5.0"
> SDKGCCVERSION = "5.0"
>
> in local.conf

  i assume this new layer should be used *in place* of the current OE
layer for testing purposes?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] [RFT] gcc 5.0 recipes available for testing

[Khem Raj]

> On Feb 20, 2015, at 3:04 AM, Robert P. J. Day  wrote:
> 
> On Fri, 20 Feb 2015, Khem Raj wrote:
> 
>> Hi All
>> 
>> Encouraged by help received on testing out glibc 2.21, now  I have put 
>> together OE recipes for gcc-5
>> 
>> GCC 5.0 is in prerelease stage 4 ( open for regression and doc fixes only)
>> 
>> https://gcc.gnu.org/ml/gcc/2015-01/msg00156.html
>> 
>> The recipes are available here
>> 
>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-5.0
>> 
>> you just need the topmost commit and then set
>> 
>> GCCVERSION = "5.0"
>> SDKGCCVERSION = "5.0"
>> 
>> in local.conf
> 
>  i assume this new layer should be used *in place* of the current OE
> layer for testing purposes?

Not really, you can do following to grab just the patch on top of your working 
branch ( of course OE-Core master snapshot don’t try on older releases)

git remote add contrib git://git.openembedded.org/openembedded-core-contrib
git fetch contrib
git cherry-pick 85cf9c0e77378ca8f93868e9f91001214c8d8f3e

> 
> rday
> 
> -- 
> 
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
>http://crashcourse.ca
> 
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 

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

Re: [yocto] [RFT] gcc 5.0 recipes available for testing

[Robert P. J. Day]

On Fri, 20 Feb 2015, Khem Raj wrote:

>
> > On Feb 20, 2015, at 3:04 AM, Robert P. J. Day  wrote:
> >
> > On Fri, 20 Feb 2015, Khem Raj wrote:
> >
> >> Hi All
> >>
> >> Encouraged by help received on testing out glibc 2.21, now  I have put 
> >> together OE recipes for gcc-5
> >>
> >> GCC 5.0 is in prerelease stage 4 ( open for regression and doc fixes only)
> >>
> >> https://gcc.gnu.org/ml/gcc/2015-01/msg00156.html
> >>
> >> The recipes are available here
> >>
> >> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-5.0
> >>
> >> you just need the topmost commit and then set
> >>
> >> GCCVERSION = "5.0"
> >> SDKGCCVERSION = "5.0"
> >>
> >> in local.conf
> >
> >  i assume this new layer should be used *in place* of the current OE
> > layer for testing purposes?
>
> Not really, you can do following to grab just the patch on top of your 
> working branch ( of course OE-Core master snapshot don’t try on older 
> releases)
>
> git remote add contrib git://git.openembedded.org/openembedded-core-contrib
> git fetch contrib
> git cherry-pick 85cf9c0e77378ca8f93868e9f91001214c8d8f3e

  ah, gotcha.

rday

p.s. i fixed the OE core mailing list address for you. :-)

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Edit project specific config files of other recipe like /etc/ssh/ssh_config from openssh

[Kai Ulrich]

Hi,

I create a layer for my project.
How can I edit (patch?)  project specific config files of other recipe for
the rootfs without touching the original recipe.
Project specific config files could by /etc/ssh/ssh_config (do not touch
recipe openssh )

Friendly regrades
Kai Ulrich
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] glibc fetching problems

[Gary Thomas]

I just updated Poky/Yocto to the latest master and now I get
this failure:
ERROR: Function failed: Fetcher failure for URL: 
'git://sourceware.org/git/glibc.git;branch=release/2.21/master'. Unable to 
fetch URL from any source.

This is because any attempt to clone that repo breaks:
  $ git clone git://sourceware.org/git/glibc.git
  Cloning into 'glibc'...
  fatal: read error: Connection reset by peer

It's not a local networking issue - I tried it on both sides
of the pond.

Sadly, the yocto mirrors don't have this file either - the latest
tarball in http://downloads.yoctoproject.org/mirror/sources/
only goes up to 2.20

Any ideas, given that the 2.20 recipes have been replaced?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] glibc fetching problems

[Burton, Ross]

On 20 February 2015 at 12:50, Gary Thomas  wrote:

> This is because any attempt to clone that repo breaks:
>   $ git clone git://sourceware.org/git/glibc.git
>   Cloning into 'glibc'...
>   fatal: read error: Connection reset by peer
>

Works for me:

$ git clone git://sourceware.org/git/glibc.git
Cloning into 'glibc'...
remote: Counting objects: 408341, done
...

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

Re: [yocto] glibc fetching problems

[Gary Thomas]

On 2015-02-20 06:16, Burton, Ross wrote:


On 20 February 2015 at 12:50, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

This is because any attempt to clone that repo breaks:
   $ git clone git://sourceware.org/git/__glibc.git 

   Cloning into 'glibc'...
   fatal: read error: Connection reset by peer


Works for me:

$ git clone git://sourceware.org/git/glibc.git 

Cloning into 'glibc'...
remote: Counting objects: 408341, done
...

Transient error?


Must have been, it's working for me now as well.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] glibc fetching problems

[Burton, Ross]

On 20 February 2015 at 13:19, Gary Thomas  wrote:

> Transient error?
>>
>
> Must have been, it's working for me now as well.


My magic touch. ;)

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

Re: [yocto] Edit project specific config files of other recipe like /etc/ssh/ssh_config from openssh

[Chris Hallinan]

Hi Kai,

In your layer, create a .bbappend matching the basename of the package
you want to change. Using your example, create
recipes-connectivity/openssh/openssh_6.6p1.bbappend (make sure
versions match).

Then you can either replace or patch ssh_config. I would patch it.
Create your patch, put it in recipes-connectivity/openssh/files, and
name your patch file, ending in .patch in SRC_URI in your .bbappend
file.

Your .bbappend file might look something like this:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += "file://myssh_config.patch"

The first line instructs bitbake where to search for your patch file.
The second line will cause the file to be fetched into your ${WORKDIR}
for openssh, and because it has a .patch extension, it will
automatically be applied.

The excellent Yocto Project Developer Manual has an example of a
.bbappend file, although its slightly outdated.  You no longer need PR
field, and SRC_URI should be += instead of "=".

http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#using-bbappend-files

Yocto Project is gifted with some of the best documentation in the
open source world.

Good luck!

On Fri, Feb 20, 2015 at 7:18 AM, Kai Ulrich  wrote:
> Hi,
>
> I create a layer for my project.
> How can I edit (patch?)  project specific config files of other recipe for
> the rootfs without touching the original recipe.
> Project specific config files could by /etc/ssh/ssh_config (do not touch
> recipe openssh )
>
> Friendly regrades
> Kai Ulrich
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Life is like Linux - it never stands still.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] WARNING: Could not copy license file LICENSE -> Downloaded archive structure?

[Kai Ulrich]

Hi,

I working on a smstools3 recipe.

after running bitbake smstools3

I got following
WARNING: Could not copy license file LICENSE: [Errno 2] No such file or
directory:
'/home/kulrich/Develpment/yocto/dizzy/poky/build_test/tmp/work/i586-poky-linux/smstools3/3.1.15-r0/smstools3-3.1.15/LICENSE'
Function failed: smstools3: LIC_FILES_CHKSUM points to an invalid file:
.../yocto/dizzy/poky/build_test/tmp/work/i586-poky-linux/smstools3/3.1.15-r0/smstools3-3.1.15/LICENSE

After looking for the LICENSE found it under
.../yocto/dizzy/poky/build_test/tmp/work/i586-poky-linux/smstools3/3.1.15-r0/smstools/LICENSE

It seams the reason is the Package structure of the smstools3-3.1.15.tar.gz.
it is

smstools3-3.1.15.tar.gz.
---smstools3
---src
---scripts
---examples
---doc
---uninstall.sh
---README
---package.sh
---Makefile
---LICENSE

with a struktur (2) like

smstools3-3.1.15.tar.gz.
---smstools3-3.1.15
---src
---scripts
---examples
---doc
---uninstall.sh
---README
---package.sh
---Makefile
---LICENSE

it works fine.

Any idea how I can configure my recipe that that it works with the original
package structure?

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

Re: [yocto] [meta-raspberrypi][PATCH 1/1] layer.conf: set layer depends

[Petter Mabäcker]

 

After discussions with meta-raspberrypi maintainers we have come to
the conclusion that we will not set any layer depends. We shouldn't
break most of the builds which don't use the test image and therefore
don't need the multimedia layer. So will instead break out the 'layer
prio' part and send out in a separate review. 

/Petter 

2015-02-10
23:39 skrev Petter Mabäcker: 

> Ensure that build fails in a
informative way if not all layer
> requirements are fulfilled.
> 
> To
disable strict layer depend set 'LAYERDEPENDS_raspberrypi = ""'
> in
local.conf.
> 
> Also set a high layer prio to ensure that
meta-raspberrypi addons
> are always prioritized above the depended
layers.
> 
> [Feature #46]
> 
> Change-Id:
I8df772a59975ae379c3a1e93e2770e83be752bfd
> Signed-off-by: Petter
Mabäcker 
> ---
> README | 4 
> conf/layer.conf |
3 ++-
> 2 files changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git
a/README b/README
> index bb2f4be..3dad1ea 100644
> --- a/README
> +++
b/README
> @@ -143,6 +143,10 @@ See:
http://wayland.freedesktop.org/raspberrypi.html [1]
> 
> 2.H. Images
>
===
> +Note: 'rpi-hwup-image' and 'rpi-basic-image' can be build
without
> + meta-multimedia. Set 'LAYERDEPENDS_raspberrypi = ""' in
local.conf
> + to enable build without 'meta-multimedia'.
> +
> *
rpi-hwup-image
> Hardware up image
> * rpi-basic-image
> diff --git
a/conf/layer.conf b/conf/layer.conf
> index 7bffd4b..b5ab695 100644
>
--- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -7,7 +7,8 @@ BBFILES
+= "${LAYERDIR}/recipes*/*/*.bb 
> 
> BBFILE_COLLECTIONS +=
"raspberrypi"
> BBFILE_PATTERN_raspberrypi := "^${LAYERDIR}/"
>
-BBFILE_PRIORITY_raspberrypi = "6"
> +BBFILE_PRIORITY_raspberrypi =
"9"
> +LAYERDEPENDS_raspberrypi = "multimedia-layer"
> 
> # Additional
license directories.
> LICENSE_PATH +=
"${LAYERDIR}/files/custom-licenses"
> -- 
> 1.9.1
 

Links:
--
[1]
http://wayland.freedesktop.org/raspberrypi.html
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/1] layer.conf: set high layer priority

[Petter Mabäcker]

Set a high layer prio to ensure that meta-raspberrypi addons
are always prioritized above the depended layers.

Signed-off-by: Petter Mabäcker 
---
 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 7bffd4b..bea5a65 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -7,7 +7,7 @@ BBFILES += "${LAYERDIR}/recipes*/*/*.bb \
 
 BBFILE_COLLECTIONS += "raspberrypi"
 BBFILE_PATTERN_raspberrypi := "^${LAYERDIR}/"
-BBFILE_PRIORITY_raspberrypi = "6"
+BBFILE_PRIORITY_raspberrypi = "9"
 
 # Additional license directories.
 LICENSE_PATH += "${LAYERDIR}/files/custom-licenses"
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Petter Mabäcker]

The following changes since commit d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:

  README: Github repo changed (2015-02-14 02:00:57 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio

Petter Mabäcker (1):
  layer.conf: set high layer priority

 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
1.9.1

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

Re: [yocto] [PATCH] Add mpich support

[Alexandru Vaduva]

Yes, it is my opinion that adding to RDPENDS libxml2 and libpciaccess and 
changing the /bin/csh and /bin/bash to /bin/sh should solve those warnings.
The Warnings are related with the patch done by Richard Yang. Here`s a 
link:[OE-core] [PATCH 0/6] meta: fix rdepends issues for test related packages
|   |
|   |   |   |   |   |
| [OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
packages[OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
packages Robert Yang liezhi.yang at windriver.com Mon Aug 18 06:06:31 UTC 2014  
|
|  |
| View on lists.openembedded.org | Preview by Yahoo |
|  |
|   |

Hope I am not wrong  with my assumption, but I am pretty sure about this one ;)

Alex Vaduva


 On Friday, February 20, 2015 6:19 PM, "Rodriguez Bahena, Victor" 
 wrote:
   

 So let me see if I understand, the following error ( build log from this
patch): 

NOTE: Executing RunQueue Tasks
ERROR: QA Issue: package mpich contains bad
RPATH /home/vrodri3/poky/build/tmp/sysroots/qemux86/usr/lib in
file 
/home/vrodri3/poky/build/tmp/work/i586-poky-linux/mpich/3.1.1-r0/packages-split/mpich/usr/bin/i586-poky-linux-mpiexec.hydra
 [rpaths]
WARNING: QA Issue: mpich rdepends on libxml2, but it isn't a build
dependency? [build-deps]
WARNING: QA Issue: mpich rdepends on libpciaccess, but it isn't a build
dependency? [build-deps]
WARNING: QA Issue: mpich requires /usr/bin/bash, but no providers in its
RDEPENDS [file-rdeps]
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored
in: 
/home/vrodri3/poky/build/tmp/work/i586-poky-linux/mpich/3.1.1-r0/temp/log.do_package_qa.20022
ERROR: Task 9
(/home/vrodri3/meta-openembedded/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb, 
do_package_qa) failed with exit code '1'
NOTE: Tasks Summary: Attempted 667 tasks of which 646 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:


Is due to the fact that some of the QA scripts need sh instead of bash
( or something similar ) ? 

I am a little bit lost here 

Thanks for the help

Victor Rodriguez



On Thu, 2015-02-19 at 21:49 +, Alexandru Vaduva wrote:
> Forgot to mention that I identified the line:
> src/pm/hydra/tools/topo/hwloc/hwloc/contrib/hg/set-hg-share-perms.csh:1:#!/bin/csh
>  -f
> 
> 
> It seems that one script uses /bin/ch, and also another one
> using /bin/bash.
> Adding RDEPENDS_${PN} += "bash perl tcsh" did not solved the problem.
> but maybe changing them o /bin/sh will do.
> The idea is similar to the change from 
> 
> meta/recipes-extended/lsb/lsbtest/LSB_Test.s
> Link: [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh  
> 
>  
>  
>  
>  
>  
>  
> [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh
> [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh Robert Yang
> liezhi.yang at windriver.com Wed Aug 27 15:57:11 UTC 2014 
> 
> View on lists.openembedded.org
> Preview by Yahoo
> 
>  
> What do you say?
> 
> 
> 
> 
> Alex Vaduva
> 
> 
> 
> On Thursday, February 19, 2015 11:44 PM, Alexandru. Vaduva
>  wrote:
> 
> 
> 
> From: Victor Rodriguez 
> 
> This patch add mpich support to yocto in order to run MPI framework on
> embedded
> systems.
> 
> Signed-off-by: Alejandro Hernandez
> 
> Signed-off-by: Victor Rodriguez 
> Signed-off-by: Alexandru.Vaduva 
> ---
> meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb | 29
> +++
> 1 file changed, 29 insertions(+)
> create mode 100644 meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> 
> diff --git a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> new file mode 100644
> index 000..2f4226e
> --- /dev/null
> +++ b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> @@ -0,0 +1,29 @@
> +SUMMARY = "Message Passing Interface(MPI) implementation"
> +HOMEPAGE = "http://git.mpich.org/mpich.git/";
> +SECTION = "devel"
> +
> +LICENSE = "BSD-2-Clause"
> +LIC_FILES_CHKSUM =
> "file://COPYRIGHT;md5=2106f0435056f3dd9349747a766e5816"
> +
> +SRC_URI =
> "http://www.mpich.org/static/downloads/${PV}/mpich-${PV}.tar.gz";
> +SRC_URI[md5sum] = "40dc408b1e03cc36d80209baaa2d32b7"
> +SRC_URI[sha256sum] =
> "455ccfaf4ec724d2cf5d8bff1f3d26a958ad196121e7ea26504fd3018757652d"
> +
> +RDEPENDS_${PN} += "bash perl tcsh"
> +S = "${WORKDIR}/${PN}-${PV}"
> +
> +EXTRA_OECONF = "--enable-debuginfo \
> +                --enable-fast \
> +                --enable-shared  \
> +                --disable-f77 \
> +                --disable-fc \
> +                --disable-fortran \
> +                --disable-cxx"
> +
> +inherit autotools-brokensep gettext
> +
> +do_configure_prepend() {
> +    autoreconf --verbose --install --force -I . -I confdb/ -I maint/
> +    oe_runconf
> +    exit
> +}
> -- 
> 1.9.1
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> 


-- 
Victor Rodriguez

Open Source Technology Center

Re: [yocto] Simple recipe quit working in dizzy

[Jim Rafert]

Hi Paul,

Thank you for taking an interest in this.

I looked at the log.do_rootfs, and didn't see anything that was immediately 
suspicious.
I have inlined the log at the end of my reply, here.

I don't see how such a simple recipe could be broken by a Yocto bug, and not 
have the 
whole thing be massively broken.   

-Jim- 

cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
DEBUG: Executing python function rootfs_process_ignore
DEBUG: Python function rootfs_process_ignore finished
DEBUG: Executing python function rootfs_runtime_mapping
DEBUG: Python function rootfs_runtime_mapping finished
DEBUG: Executing python function do_rootfs
NOTE: configuring RPM platform settings
NOTE: configuring RPM system provides
NOTE: configuring RPM DB settings
NOTE: configuring Smart settings
NOTE: Note: adding Smart channel spectra_ls (35)
NOTE: Note: adding Smart channel i586 (30)
NOTE: Note: adding Smart channel all (25)
NOTE: adding Smart RPM DB channel
NOTE: Note: configuring RPM cross-install scriptlet_wrapper
NOTE: ## Generate rootfs ###
NOTE: Executing 
'/home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo 
--update -q /home/jimr/tera/yocto/dizzy/build/tmp/deploy/rpm/i586' ...
NOTE: Installing the following packages: libgcc1 parted grub dosfstools psplash 
vim udev-extraconf rsyslog libsoci nss rpm unzip zip spectra-postbuild smartpm 
e2fsprogs-tune2fs packagegroup-core-eclipse-debug poco libstdc++6 sqlite3 
e2fsprogs-e2fsck openssl-staticdev boost packagegroup-core-ssh-openssh 
packagegroup-core-boot packagegroup-core-full-cmdline rpmresolve ntp 
e2fsprogs-mke2fs util-linux packagegroup-core-tools-debug openssl e2fsprogs 
sys-freedos e2fsprogs-badblocks locale-base-en-us locale-base-en-gb
NOTE: to be installed: libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 
psplash@i586 vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 
rpm@i586 unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 
e2fsprogs-tune2fs@i586 packagegroup-core-eclipse-debug@all poco@i586 
libstdc++6@i586 sqlite3@i586 e2fsprogs-e2fsck@i586 openssl-staticdev@i586 
boost@i586 packagegroup-core-ssh-openssh@all packagegroup-core-boot@spectra_ls 
packagegroup-core-full-cmdline@all rpmresolve@i586 ntp@i586 
e2fsprogs-mke2fs@i586 util-linux@i586 packagegroup-core-tools-debug@all 
openssl@i586 e2fsprogs@i586 sys-freedos@i586 e2fsprogs-badblocks@i586 
locale-base-en-us@i586 locale-base-en-gb@i586
NOTE: /home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/smart 
--quiet 
--data-dir=/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs/var/lib/smart
 install -y libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 psplash@i586 
vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 rpm@i586 
unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 e2fsprogs-tune2fs@i586 
packagegroup-core-eclipse-debug@all poco@i586 libstdc++6@i586 sqlite3@i586 
e2fsprogs-e2fsck@i586 openssl-staticdev@i586 boost@i586 
packagegroup-core-ssh-openssh@all packagegroup-core-boot@spectra_ls 
packagegroup-core-full-cmdline@all rpmresolve@i586 ntp@i586 
e2fsprogs-mke2fs@i586 util-linux@i586 packagegroup-core-tools-debug@all 
openssl@i586 e2fsprogs@i586 sys-freedos@i586 e2fsprogs-badblocks@i586 
locale-base-en-us@i586 locale-base-en-gb@i586
NOTE: Output from bash-4.3-r0@i586:
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/sh
 to /bin/bash
Output from busybox-1.22.1-r32@i586:
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/ar
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/gunzip
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/zcat
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/bunzip2
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/bzcat
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/cpio
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/gzip
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/tar
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

[Richard Purdie]

On Mon, 2015-02-02 at 02:02 -0800, Khem Raj wrote:
> I have put together upgrade to gcc 4.9.2 as well as glibc 2.21 (
> upcoming ) on  a contrib branch ( top 2 patches) its has not got much
> testing besides x86 qemu thus far.
> 
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-glibc-upgrade
> 
> I would like to request some help in testing these out in your
> respective environments and please report any issues you see so we can
> start sorting them out at earlier and making its way into OE-Core.
> 
> Thanks for your help

For info, I've now merged the glibc part of this change now too.

Khem: Thanks for the work on this!

Cheers,

Richard



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

Re: [yocto] WARNING: Could not copy license file LICENSE -> Downloaded archive structure?

[akuster808]

Kai,


On 02/20/2015 06:44 AM, Kai Ulrich wrote:

Hi,

I working on a smstools3 recipe.

after running bitbake smstools3

I got following
WARNING: Could not copy license file LICENSE: [Errno 2] No such file or
directory:
'/home/kulrich/Develpment/yocto/dizzy/poky/build_test/tmp/work/i586-poky-linux/smstools3/3.1.15-r0/smstools3-3.1.15/LICENSE'
Function failed: smstools3: LIC_FILES_CHKSUM points to an invalid file:
.../yocto/dizzy/poky/build_test/tmp/work/i586-poky-linux/smstools3/3.1.15-r0/smstools3-3.1.15/LICENSE

After looking for the LICENSE found it under
.../yocto/dizzy/poky/build_test/tmp/work/i586-poky-linux/smstools3/3.1.15-r0/smstools/LICENSE

It seams the reason is the Package structure of the smstools3-3.1.15.tar.gz.
it is

smstools3-3.1.15.tar.gz.
---smstools3
---src
---scripts
---examples
---doc
---uninstall.sh
---README
---package.sh
---Makefile
---LICENSE

with a struktur (2) like

smstools3-3.1.15.tar.gz.
---smstools3-3.1.15
---src
---scripts
---examples
---doc
---uninstall.sh
---README
---package.sh
---Makefile
---LICENSE

it works fine.

Any idea how I can configure my recipe that that it works with the
original package structure?



You might need to override the source directory in the recipe.

S = "${WORKDIR}/${BP}"

- Armin


Kai Ulrich





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

Re: [yocto] [PATCH] Add mpich support

[Aníbal Limón]

Hi all,

The issue for shell are because DEPENDS includes tcsh i remove it, also 
i fixed the rpath issue passing to the
OE_EXTRACONF --disable-rpath but still exists problem building with 
hydra pm (default) i changed to gforker.


I think the Hydra issues are for some Makefiles contains -rpath but it 
need more debug, here is the two patches that

actually works.

Kind regards,
alimon


On 20/02/15 11:01, Alexandru Vaduva wrote:

Yes, it is my opinion that adding to RDPENDS libxml2 and libpciaccess and 
changing the /bin/csh and /bin/bash to /bin/sh should solve those warnings.
The Warnings are related with the patch done by Richard Yang. Here`s a 
link:[OE-core] [PATCH 0/6] meta: fix rdepends issues for test related packages
|   |
|   |   |   |   |   |
| [OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
packages[OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
packages Robert Yang liezhi.yang at windriver.com Mon Aug 18 06:06:31 UTC 2014  
|
|  |
| View on lists.openembedded.org | Preview by Yahoo |
|  |
|   |

Hope I am not wrong  with my assumption, but I am pretty sure about this one ;)

Alex Vaduva


  On Friday, February 20, 2015 6:19 PM, "Rodriguez Bahena, Victor" 
 wrote:



  So let me see if I understand, the following error ( build log from this
patch):

NOTE: Executing RunQueue Tasks
ERROR: QA Issue: package mpich contains bad
RPATH /home/vrodri3/poky/build/tmp/sysroots/qemux86/usr/lib in
file 
/home/vrodri3/poky/build/tmp/work/i586-poky-linux/mpich/3.1.1-r0/packages-split/mpich/usr/bin/i586-poky-linux-mpiexec.hydra
 [rpaths]
WARNING: QA Issue: mpich rdepends on libxml2, but it isn't a build
dependency? [build-deps]
WARNING: QA Issue: mpich rdepends on libpciaccess, but it isn't a build
dependency? [build-deps]
WARNING: QA Issue: mpich requires /usr/bin/bash, but no providers in its
RDEPENDS [file-rdeps]
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored
in: 
/home/vrodri3/poky/build/tmp/work/i586-poky-linux/mpich/3.1.1-r0/temp/log.do_package_qa.20022
ERROR: Task 9
(/home/vrodri3/meta-openembedded/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb, 
do_package_qa) failed with exit code '1'
NOTE: Tasks Summary: Attempted 667 tasks of which 646 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:


Is due to the fact that some of the QA scripts need sh instead of bash
( or something similar ) ?

I am a little bit lost here

Thanks for the help

Victor Rodriguez



On Thu, 2015-02-19 at 21:49 +, Alexandru Vaduva wrote:

Forgot to mention that I identified the line:
src/pm/hydra/tools/topo/hwloc/hwloc/contrib/hg/set-hg-share-perms.csh:1:#!/bin/csh
 -f


It seems that one script uses /bin/ch, and also another one
using /bin/bash.
Adding RDEPENDS_${PN} += "bash perl tcsh" did not solved the problem.
but maybe changing them o /bin/sh will do.
The idea is similar to the change from

meta/recipes-extended/lsb/lsbtest/LSB_Test.s
Link: [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh

   
   
   
   
   
   
[OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh

[OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh Robert Yang
liezhi.yang at windriver.com Wed Aug 27 15:57:11 UTC 2014

View on lists.openembedded.org
Preview by Yahoo

   
What do you say?





Alex Vaduva



On Thursday, February 19, 2015 11:44 PM, Alexandru. Vaduva
 wrote:



From: Victor Rodriguez 

This patch add mpich support to yocto in order to run MPI framework on
embedded
systems.

Signed-off-by: Alejandro Hernandez

Signed-off-by: Victor Rodriguez 
Signed-off-by: Alexandru.Vaduva 
---
meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb | 29
+++
1 file changed, 29 insertions(+)
create mode 100644 meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb

diff --git a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
new file mode 100644
index 000..2f4226e
--- /dev/null
+++ b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
@@ -0,0 +1,29 @@
+SUMMARY = "Message Passing Interface(MPI) implementation"
+HOMEPAGE = "http://git.mpich.org/mpich.git/";
+SECTION = "devel"
+
+LICENSE = "BSD-2-Clause"
+LIC_FILES_CHKSUM =
"file://COPYRIGHT;md5=2106f0435056f3dd9349747a766e5816"
+
+SRC_URI =
"http://www.mpich.org/static/downloads/${PV}/mpich-${PV}.tar.gz";
+SRC_URI[md5sum] = "40dc408b1e03cc36d80209baaa2d32b7"
+SRC_URI[sha256sum] =
"455ccfaf4ec724d2cf5d8bff1f3d26a958ad196121e7ea26504fd3018757652d"
+
+RDEPENDS_${PN} += "bash perl tcsh"
+S = "${WORKDIR}/${PN}-${PV}"
+
+EXTRA_OECONF = "--enable-debuginfo \
+--enable-fast \
+--enable-shared  \
+--disable-f77 \
+--disable-fc \
+--disable-fortran \
+--disable-cxx"
+
+inherit autotools-brokensep gettext
+
+do_configure_prepend() {
+autoreconf --verbose --install --force -I . -I confdb/ -I main

Re: [yocto] [PATCH] Add mpich support

[Rodriguez Bahena, Victor]

Thanks a lot Anibal 

That work just fine !!! 

Working on a clean version in order to send ever oe-core mailing list

Regards


-- 
Victor Rodriguez

Open Source Technology Center

On Fri, 2015-02-20 at 15:43 -0600, Aníbal Limón wrote:
> Hi all,
> 
> The issue for shell are because DEPENDS includes tcsh i remove it,
> also i fixed the rpath issue passing to the
> OE_EXTRACONF --disable-rpath but still exists problem building with
> hydra pm (default) i changed to gforker.
> 
> I think the Hydra issues are for some Makefiles contains -rpath but it
> need more debug, here is the two patches that
> actually works.
> 
> Kind regards,
> alimon
> 
> 
> On 20/02/15 11:01, Alexandru Vaduva wrote:
> 
> > Yes, it is my opinion that adding to RDPENDS libxml2 and libpciaccess and 
> > changing the /bin/csh and /bin/bash to /bin/sh should solve those warnings.
> > The Warnings are related with the patch done by Richard Yang. Here`s a 
> > link:[OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
> > packages
> > |   |
> > |   |   |   |   |   |
> > | [OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
> > packages[OE-core] [PATCH 0/6] meta: fix rdepends issues for test related 
> > packages Robert Yang liezhi.yang at windriver.com Mon Aug 18 06:06:31 UTC 
> > 2014  |
> > |  |
> > | View on lists.openembedded.org | Preview by Yahoo |
> > |  |
> > |   |
> > 
> > Hope I am not wrong  with my assumption, but I am pretty sure about this 
> > one ;)
> > 
> > Alex Vaduva
> > 
> > 
> >  On Friday, February 20, 2015 6:19 PM, "Rodriguez Bahena, Victor" 
> >  wrote:
> >
> > 
> >  So let me see if I understand, the following error ( build log from this
> > patch): 
> > 
> > NOTE: Executing RunQueue Tasks
> > ERROR: QA Issue: package mpich contains bad
> > RPATH /home/vrodri3/poky/build/tmp/sysroots/qemux86/usr/lib in
> > file 
> > /home/vrodri3/poky/build/tmp/work/i586-poky-linux/mpich/3.1.1-r0/packages-split/mpich/usr/bin/i586-poky-linux-mpiexec.hydra
> >  [rpaths]
> > WARNING: QA Issue: mpich rdepends on libxml2, but it isn't a build
> > dependency? [build-deps]
> > WARNING: QA Issue: mpich rdepends on libpciaccess, but it isn't a build
> > dependency? [build-deps]
> > WARNING: QA Issue: mpich requires /usr/bin/bash, but no providers in its
> > RDEPENDS [file-rdeps]
> > ERROR: QA run found fatal errors. Please consider fixing them.
> > ERROR: Function failed: do_package_qa
> > ERROR: Logfile of failure stored
> > in: 
> > /home/vrodri3/poky/build/tmp/work/i586-poky-linux/mpich/3.1.1-r0/temp/log.do_package_qa.20022
> > ERROR: Task 9
> > (/home/vrodri3/meta-openembedded/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb,
> >  do_package_qa) failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 667 tasks of which 646 didn't need to be
> > rerun and 1 failed.
> > Waiting for 0 running tasks to finish:
> > 
> > 
> > Is due to the fact that some of the QA scripts need sh instead of bash
> > ( or something similar ) ? 
> > 
> > I am a little bit lost here 
> > 
> > Thanks for the help
> > 
> > Victor Rodriguez
> > 
> > 
> > 
> > On Thu, 2015-02-19 at 21:49 +, Alexandru Vaduva wrote:
> > > Forgot to mention that I identified the line:
> > > src/pm/hydra/tools/topo/hwloc/hwloc/contrib/hg/set-hg-share-perms.csh:1:#!/bin/csh
> > >  -f
> > > 
> > > 
> > > It seems that one script uses /bin/ch, and also another one
> > > using /bin/bash.
> > > Adding RDEPENDS_${PN} += "bash perl tcsh" did not solved the problem.
> > > but maybe changing them o /bin/sh will do.
> > > The idea is similar to the change from 
> > > 
> > > meta/recipes-extended/lsb/lsbtest/LSB_Test.s
> > > Link: [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh  
> > > 
> > >   
> > >   
> > >   
> > >   
> > >   
> > >   
> > > [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh
> > > [OE-core] [PATCH 6/9] lsbtest: no bashism in LSB_Test.sh Robert Yang
> > > liezhi.yang at windriver.com Wed Aug 27 15:57:11 UTC 2014 
> > > 
> > > View on lists.openembedded.org
> > > Preview by Yahoo
> > > 
> > >   
> > > What do you say?
> > > 
> > > 
> > > 
> > > 
> > > Alex Vaduva
> > > 
> > > 
> > > 
> > > On Thursday, February 19, 2015 11:44 PM, Alexandru. Vaduva
> > >  wrote:
> > > 
> > > 
> > > 
> > > From: Victor Rodriguez 
> > > 
> > > This patch add mpich support to yocto in order to run MPI framework on
> > > embedded
> > > systems.
> > > 
> > > Signed-off-by: Alejandro Hernandez
> > > 
> > > Signed-off-by: Victor Rodriguez 
> > > Signed-off-by: Alexandru.Vaduva 
> > > ---
> > > meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb | 29
> > > +++
> > > 1 file changed, 29 insertions(+)
> > > create mode 100644 meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> > > 
> > > diff --git a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> > > b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> > > new file mode 100644
> > > index 000..2f4226e
> > > --- /dev/null
> > > +++ b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
> > >

Re: [yocto] Simple recipe quit working in dizzy

[akuster]

On 02/20/2015 09:49 AM, Jim Rafert wrote:

Hi Paul,

Thank you for taking an interest in this.

I looked at the log.do_rootfs, and didn't see anything that was immediately 
suspicious.
I have inlined the log at the end of my reply, here.

I don't see how such a simple recipe could be broken by a Yocto bug, and not 
have the
whole thing be massively broken.


Is it possible for you to try your recipe on 'master'? that might tell 
use if something is missing in dizzy.



- Armin


-Jim-

cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
DEBUG: Executing python function rootfs_process_ignore
DEBUG: Python function rootfs_process_ignore finished
DEBUG: Executing python function rootfs_runtime_mapping
DEBUG: Python function rootfs_runtime_mapping finished
DEBUG: Executing python function do_rootfs
NOTE: configuring RPM platform settings
NOTE: configuring RPM system provides
NOTE: configuring RPM DB settings
NOTE: configuring Smart settings
NOTE: Note: adding Smart channel spectra_ls (35)
NOTE: Note: adding Smart channel i586 (30)
NOTE: Note: adding Smart channel all (25)
NOTE: adding Smart RPM DB channel
NOTE: Note: configuring RPM cross-install scriptlet_wrapper
NOTE: ## Generate rootfs ###
NOTE: Executing 
'/home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo 
--update -q /home/jimr/tera/yocto/dizzy/build/tmp/deploy/rpm/i586' ...
NOTE: Installing the following packages: libgcc1 parted grub dosfstools psplash 
vim udev-extraconf rsyslog libsoci nss rpm unzip zip spectra-postbuild smartpm 
e2fsprogs-tune2fs packagegroup-core-eclipse-debug poco libstdc++6 sqlite3 
e2fsprogs-e2fsck openssl-staticdev boost packagegroup-core-ssh-openssh 
packagegroup-core-boot packagegroup-core-full-cmdline rpmresolve ntp 
e2fsprogs-mke2fs util-linux packagegroup-core-tools-debug openssl e2fsprogs 
sys-freedos e2fsprogs-badblocks locale-base-en-us locale-base-en-gb
NOTE: to be installed: libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 
psplash@i586 vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 
rpm@i586 unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 
e2fsprogs-tune2fs@i586 packagegroup-core-eclipse-debug@all poco@i586 
libstdc++6@i586 sqlite3@i586 e2fsprogs-e2fsck@i586 openssl-staticdev@i586 
boost@i586 packagegroup-core-ssh-openssh@all packagegroup-core-boot@spectra_ls 
packagegroup-core-full-cmdline@all rpmresolve@i586 ntp@i586 
e2fsprogs-mke2fs@i586 util-linux@i586 packagegroup-core-tools-debug@all 
openssl@i586 e2fsprogs@i586 sys-freedos@i586 e2fsprogs-badblocks@i586 
locale-base-en-us@i586 locale-base-en-gb@i586
NOTE: /home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/smart 
--quiet 
--data-dir=/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs/var/lib/smart
 install -y libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 psplash@i586 
vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 rpm@i586 
unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 e2fsprogs-tune2fs@i586 
packagegroup-core-eclipse-debug@all poco@i586 libstdc++6@i586 sqlite3@i586 
e2fsprogs-e2fsck@i586 openssl-staticdev@i586 boost@i586 
packagegroup-core-ssh-openssh@all packagegroup-core-boot@spectra_ls 
packagegroup-core-full-cmdline@all rpmresolve@i586 ntp@i586 
e2fsprogs-mke2fs@i586 util-linux@i586 packagegroup-core-tools-debug@all 
openssl@i586 e2fsprogs@i586 sys-freedos@i586 e2fsprogs-badblocks@i586 
locale-base-en-us@i586 locale-base-en-gb@i586
NOTE: Output from bash-4.3-r0@i586:
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/sh
 to /bin/bash
Output from busybox-1.22.1-r32@i586:
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/ar
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/gunzip
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/zcat
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/bunzip2
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/bzcat
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/cpio
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/gzip
 to /bin/busybox.nosuid
update-alternatives: Linking 
/home/jimr/tera/yocto/dizzy/build/tmp/work/s

Re: [yocto] Simple recipe quit working in dizzy

[Jim Rafert]

The recipe was working on daisy, and stopped working when ported to dizzy.



From: akuster [akus...@mvista.com]
Sent: Friday, February 20, 2015 3:28 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Simple recipe quit working in dizzy

On 02/20/2015 09:49 AM, Jim Rafert wrote:
> Hi Paul,
>
> Thank you for taking an interest in this.
>
> I looked at the log.do_rootfs, and didn't see anything that was immediately 
> suspicious.
> I have inlined the log at the end of my reply, here.
>
> I don't see how such a simple recipe could be broken by a Yocto bug, and not 
> have the
> whole thing be massively broken.

Is it possible for you to try your recipe on 'master'? that might tell
use if something is missing in dizzy.


- Armin
>
> -Jim-
>
> cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
> DEBUG: Executing python function rootfs_process_ignore
> DEBUG: Python function rootfs_process_ignore finished
> DEBUG: Executing python function rootfs_runtime_mapping
> DEBUG: Python function rootfs_runtime_mapping finished
> DEBUG: Executing python function do_rootfs
> NOTE: configuring RPM platform settings
> NOTE: configuring RPM system provides
> NOTE: configuring RPM DB settings
> NOTE: configuring Smart settings
> NOTE: Note: adding Smart channel spectra_ls (35)
> NOTE: Note: adding Smart channel i586 (30)
> NOTE: Note: adding Smart channel all (25)
> NOTE: adding Smart RPM DB channel
> NOTE: Note: configuring RPM cross-install scriptlet_wrapper
> NOTE: ## Generate rootfs ###
> NOTE: Executing 
> '/home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo
>  --update -q /home/jimr/tera/yocto/dizzy/build/tmp/deploy/rpm/i586' ...
> NOTE: Installing the following packages: libgcc1 parted grub dosfstools 
> psplash vim udev-extraconf rsyslog libsoci nss rpm unzip zip 
> spectra-postbuild smartpm e2fsprogs-tune2fs packagegroup-core-eclipse-debug 
> poco libstdc++6 sqlite3 e2fsprogs-e2fsck openssl-staticdev boost 
> packagegroup-core-ssh-openssh packagegroup-core-boot 
> packagegroup-core-full-cmdline rpmresolve ntp e2fsprogs-mke2fs util-linux 
> packagegroup-core-tools-debug openssl e2fsprogs sys-freedos 
> e2fsprogs-badblocks locale-base-en-us locale-base-en-gb
> NOTE: to be installed: libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 
> psplash@i586 vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 
> rpm@i586 unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 
> e2fsprogs-tune2fs@i586 packagegroup-core-eclipse-debug@all poco@i586 
> libstdc++6@i586 sqlite3@i586 e2fsprogs-e2fsck@i586 openssl-staticdev@i586 
> boost@i586 packagegroup-core-ssh-openssh@all 
> packagegroup-core-boot@spectra_ls packagegroup-core-full-cmdline@all 
> rpmresolve@i586 ntp@i586 e2fsprogs-mke2fs@i586 util-linux@i586 
> packagegroup-core-tools-debug@all openssl@i586 e2fsprogs@i586 
> sys-freedos@i586 e2fsprogs-badblocks@i586 locale-base-en-us@i586 
> locale-base-en-gb@i586
> NOTE: 
> /home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/smart 
> --quiet 
> --data-dir=/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs/var/lib/smart
>  install -y libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 psplash@i586 
> vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 rpm@i586 
> unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 
> e2fsprogs-tune2fs@i586 packagegroup-core-eclipse-debug@all poco@i586 
> libstdc++6@i586 sqlite3@i586 e2fsprogs-e2fsck@i586 openssl-staticdev@i586 
> boost@i586 packagegroup-core-ssh-openssh@all 
> packagegroup-core-boot@spectra_ls packagegroup-core-full-cmdline@all 
> rpmresolve@i586 ntp@i586 e2fsprogs-mke2fs@i586 util-linux@i586 
> packagegroup-core-tools-debug@all openssl@i586 e2fsprogs@i586 
> sys-freedos@i586 e2fsprogs-badblocks@i586 locale-base-en-us@i586 
> locale-base-en-gb@i586
> NOTE: Output from bash-4.3-r0@i586:
> update-alternatives: Linking 
> /home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/sh
>  to /bin/bash
> Output from busybox-1.22.1-r32@i586:
> update-alternatives: Linking 
> /home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/ar
>  to /bin/busybox.nosuid
> update-alternatives: Linking 
> /home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/gunzip
>  to /bin/busybox.nosuid
> update-alternatives: Linking 
> /home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//bin/zcat
>  to /bin/busybox.nosuid
> update-alternatives: Linking 
> /home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/bin/bunzip2
>  to /bin/busybox.nosuid
> update-alternatives: Linking 
> /home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs//usr/b

[yocto] [meta-selinux][PATCH] policycoreutils: address QA issues

[Joe MacDonald]

Both the fixfiles and sandbox utilities had dependencies on bash when they
didn't really need to.  Update sandbox and patch fixfiles.  ifgen is
python script, so ensure that python is listed as a runtime dependency.

Signed-off-by: Joe MacDonald 
---
 recipes-security/selinux/policycoreutils.inc   |  7 +-
 .../policycoreutils-fixfiles-de-bashify.patch  | 92 ++
 .../policycoreutils-sandbox-de-bashify.patch   | 39 +
 3 files changed, 136 insertions(+), 2 deletions(-)
 create mode 100644 
recipes-security/selinux/policycoreutils/policycoreutils-fixfiles-de-bashify.patch
 create mode 100644 
recipes-security/selinux/policycoreutils/policycoreutils-sandbox-de-bashify.patch

diff --git a/recipes-security/selinux/policycoreutils.inc 
b/recipes-security/selinux/policycoreutils.inc
index 44a5861..4846683 100644
--- a/recipes-security/selinux/policycoreutils.inc
+++ b/recipes-security/selinux/policycoreutils.inc
@@ -7,7 +7,10 @@ context."
 SECTION = "base"
 LICENSE = "GPLv2+"
 
-SRC_URI += "${@bb.utils.contains('DISTRO_FEATURES', 'pam', '${PAM_SRC_URI}', 
'', d)}"
+SRC_URI += "${@bb.utils.contains('DISTRO_FEATURES', 'pam', '${PAM_SRC_URI}', 
'', d)} \
+file://policycoreutils-fixfiles-de-bashify.patch \
+file://policycoreutils-sandbox-de-bashify.patch \
+   "
 
 PAM_SRC_URI = "file://pam.d/newrole \
file://pam.d/run_init \
@@ -97,7 +100,7 @@ RDEPENDS_${BPN}-sepolicy += "\
 "
 # static link to libsepol
 DEPENDS_${BPN}-sepolgen-ifgen += "libsepol"
-RDEPENDS_${BPN}-sepolgen-ifgen += "libselinux-python"
+RDEPENDS_${BPN}-sepolgen-ifgen += "python libselinux-python"
 RDEPENDS_${BPN}-sestatus += "libselinux"
 RDEPENDS_${BPN}-setfiles += "\
libselinux \
diff --git 
a/recipes-security/selinux/policycoreutils/policycoreutils-fixfiles-de-bashify.patch
 
b/recipes-security/selinux/policycoreutils/policycoreutils-fixfiles-de-bashify.patch
new file mode 100644
index 000..44d7525
--- /dev/null
+++ 
b/recipes-security/selinux/policycoreutils/policycoreutils-fixfiles-de-bashify.patch
@@ -0,0 +1,92 @@
+From 25ca94680f2fe20f49b80e8b5b180a0dbb903f17 Mon Sep 17 00:00:00 2001
+From: Joe MacDonald 
+Date: Fri, 20 Feb 2015 17:00:19 -0500
+Subject: [PATCH] fixfiles: de-bashify
+
+Most of the bashisms in fixfiles are pretty easy to work around, the only
+complex one is the use of PIPESTATUS.  The common solution to this is to
+use fifos but considering the action this script is performing, that's not
+necessarily the best option here.  Introducing a second invocation of rpm
+is minimal overhead on an operation that should happen very infrequently,
+so we'll try that instead.
+
+Upstream-Status: Pending
+
+Signed-off-by: Joe MacDonald 
+---
+ scripts/fixfiles | 26 +++---
+ 1 file changed, 15 insertions(+), 11 deletions(-)
+
+diff --git a/scripts/fixfiles b/scripts/fixfiles
+index 5c29eb9..10a5078 100755
+--- a/scripts/fixfiles
 b/scripts/fixfiles
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ # fixfiles
+ #
+ # Script to restore labels on a SELinux box
+@@ -25,7 +25,7 @@
+ # number if the current kernel version is greater than 2.6.30, a negative
+ # number if the current is less than 2.6.30 and 0 if they are the same.
+ #
+-function useseclabel {
++useseclabel() {
+   VER=`uname -r`
+   SUP=2.6.30
+   expr '(' "$VER" : '\([^.]*\)' ')' '-' '(' "$SUP" : '\([^.]*\)' ')' '|' \
+@@ -91,9 +91,9 @@ exclude_dirs_from_relabelling() {
+ # skip not absolute path
+ # skip not directory
+ [ -z "${i}" ] && continue
+-[[ "${i}" =~ "^[[:blank:]]*#" ]] && continue
+-[[ ! "${i}" =~ ^/.* ]] && continue
+-[[ ! -d "${i}" ]] && continue
++echo "${i}" | egrep -q '^[[:space:]]*#' && continue
++echo "${i}" | egrep -v '^/.*' && continue
++[ ! -d "${i}" ] && continue
+ exclude_from_relabelling="$exclude_from_relabelling -e $i"
+ logit "skipping the directory $i"
+   done < /etc/selinux/fixfiles_exclude_dirs
+@@ -205,8 +205,12 @@ fi
+ }
+ 
+ rpmlist() {
+-rpm -q --qf '[%{FILESTATES} %{FILENAMES}\n]' "$1" | grep '^0 ' | cut -f2- -d 
' '
+-[ ${PIPESTATUS[0]} != 0 ] && echo "$1 not found" >/dev/stderr
++if rpm -q --qf '[%{FILESTATES} %{FILENAMES}\n]' "$1" >/dev/null
++then
++rpm -q --qf '[%{FILESTATES} %{FILENAMES}\n]' "$1" | grep '^0 ' | cut 
-f2- -d ' '
++else
++echo "$1 not found" >/dev/stderr
++fi
+ }
+ 
+ #
+@@ -233,10 +237,10 @@ if [ -n "${exclude_dirs}" ]
+ then
+   TEMPFCFILE=`mktemp ${FC}.XX`
+   test -z "$TEMPFCFILE" && exit
+-  /bin/cp -p ${FC} ${TEMPFCFILE} &>/dev/null || exit
+-  tmpdirs=${tempdirs//-e/}
+-  for p in ${tmpdirs}
++  /bin/cp -p ${FC} ${TEMPFCFILE} >/dev/null 2>&1 || exit
++  for p in ${tempdirs}
+   do
++  [ ${p} = "-e" ] && continue
+   p="${p%/}"
+   p1="${p}(/.*)? -- <>"
+   echo "${p1}" >> $TEMPFCFILE
+