Re: [yocto] kernel-module- prefix for out-of-tree modules mandatory?

[Khem Raj]

> On Oct 8, 2015, at 1:29 PM, Daniel.  wrote:
> 
> Hi all,
> 
> Is the kernel-module- prefix mandatory for out-of-tree modules
> compiled inside Yocto? And, This prefix applies to package names or
> recipe names? Should I rename my recipe file with this prefix or setup
> PN stuff?

if you inherit module bbclass then the split will happen automatically
you can name your recipe anything you like, the naming applies to out packages 
only

> 
> Cheers,
> 
> --
> "Do or do not. There is no try"
>  Yoda Master
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Remove my email from your database

[Khem Raj]

Unsubscribe from mailing list. The link is right at bottom of the email

> On Oct 8, 2015, at 4:38 AM, neerajdadhwal1...@gmail.com wrote:
> 
> Sir
> Please remove my email id . Iam frustate with ur unwanted mails.
> 
> 
> Sent from my Huawei Mobile
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Intelligent global config files setting

[Gilles CARRY]

Hi,

I have a concern regarding global config files to be put into rootfs when 
several components need to alter a common config file.
Let me explain with an example.
I have two components (recipes) that need to write options into /etc/directfbrc.
Let's call the recipes c1.bb and c2.bb and respectively optc1 and optc2, the 
options they want to write to /etc/directfbrc.

The fast (and not very clean) way to do it is to centralized all the settings 
in a single recipe but this is not what I want. For a matter of maintenance, I 
would like the option settings be attached to their respective components. If 
c1 is not required (not in dependency list) then optc1 is not set.

I tried to use ROOTFS_POSTPROCESS_COMMAND in c1.bb and c2.bb but this mechanism 
only seems to work in images recipes. (inherit core-image)
Then I considered using base-file.bbappend in directories where c1 and c2 are 
stored but this does not work as base-file.bbappend is always read even though 
c1 or c2 are disabled.

Any clue?

Thanks,
Best regards,
Gilles.

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

[yocto] VFAT patent EP 0 618 540

[Gorny Krystian]

Hi,
I have a question regarding the VFAT patent (EP 0 618 540) owned by Microsoft. 
It's about common name space for long and short filenames. I have read that 
this patent was canceled by Germany / EU, but it's still available in the US 
right? So is there a patch/option where we can activate to avoid this patent?
Thanks
Krystian


_

Krystian Gorny
Research & Development

Wipotec GmbH
Adam-Hoffmann-Str. 26
67657 Kaiserslautern

T +49.631.34146-0
F +49.631.34146-8640
http://www.wipotec.com


[http://www.wipotec.com/fileadmin/user_upload/Signatur/W_Standard.jpg]

Legal information:
Wipotec Wiege- und Positioniersysteme GmbH
HRB 2317 Kaiserslautern, Management: T. D?ppre, U. Wagner

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and delete this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can any one please tell the what is the exact difference between DEPENDS and RDEPENDS

[Vivek Per]

Hi,
 Thanks
 I have one more doubt when RDEPENDS variable depends is packages . Do you
know why RDEPENDS variable in (rootfs-image.bb recipe) which inherit
core-image. why RDEPENDS cant able to install packages in final roofs image
apart from IMAGE_INSTALL .



Thanks and regrads
 Vivek

On Thu, Oct 8, 2015 at 6:19 PM, Petter Mabäcker  wrote:

> 2015-10-08 06:37 skrev Vivek Per:
>
> Hi,
>  Can any one please tell the what is the exact difference between
> DEPENDS and RDEPENDS . I am not able to get it . How these variables are
> exactly parsed.
>
>
> -regards
> vivek
>
>
>
> Hi,
>
> I guess you already have read through the manual about the variables?
>
>
> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-RDEPENDS
>
> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-DEPENDS
>
>
>
> The overall description of the differences are (please someone correct me
> if you find my answer incorrect) that DEPENDS specifics build-time
> dependencies (e.i. other recipe files) so you should be guaranteed that all
> packages listed in the DEPENDS has been built and installed in the sysroot
> before your new package starts its configure task.
>
> RDEPENDS on the other hand, is a run-time dependency so instead of other
> recipe files RDEPENDS lists packages that should have been installed in
> order to correctly run your package on target.
>
>
> All this is explained more in detail in the manual (see above links). Also
> keep in mind that DEPENDS works with recipes and RDEPENDS with packages
> (which isn't necessary the same). Debug the PACKAGES for a specific
> variable (
> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-PACKAGES)
> in order to get a clue about what packages a recipe will generate.
>
> If you still have a hard to understanding the differences my suggestion is
> that you starts playing around a bit with them. Create a project and add
> some DEPENDS and RDEPENDS to a recipe(s), build the affected packages and
> investigate if they have been built in the expected order. This can for
> example be verified by tracking the build output or by looking through the
> cooker logs tmp/log/cooker/*.
>
> BR Petter
>
>
>
> Petter Mabäcker
>
> Technux www.technux.se
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can any one please tell the difference between DEPENDS and RDEPENDS

[Vivek Per]

Hi,
Thanks
  As i read RDEPENDS  in recipe  do_build task depends on
do_pacakge_write_rpm task (i.e packages )
 I have one more doubt when RDEPENDS variable depends is packages . Do you
know why RDEPENDS variable in (rootfs-image.bb recipe) which inherit
core-image. why RDEPENDS cant able to install packages in final roofs image
apart from IMAGE_INSTALL .



Thanks and regrads
 Vivek

On Thu, Oct 8, 2015 at 9:16 PM, Robert Berger <
gm...@reliableembeddedsystems.com> wrote:

> On 10/07/2015 09:10 AM, Vivek Per wrote:
> > Hi,
> >  Can any one please tell the what is the exact difference between
> > DEPENDS and RDEPENDS .
>
> DEPENDS:
>
> http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-DEPENDS
>
> RDEPENDS:
>
> http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
>
> > I am not able to get it . How these variables are
> > exactly parsed.
> >
>
> Do you need more info?
>
> >
> > regards
> > vivek
> >
> >
> > --
> >
>
> Regards,
>
> Robert
>
>
> ...No matter what the problem is,it's always a people problem.- Jerry
> Weinberg
>
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
>
>
> --
> ___
> 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] Can any one please tell the what is the exact difference between DEPENDS and RDEPENDS

[Burton, Ross]

On 9 October 2015 at 10:16, Vivek Per  wrote:

>  I have one more doubt when RDEPENDS variable depends is packages . Do you
> know why RDEPENDS variable in (rootfs-image.bb recipe) which inherit
> core-image. why RDEPENDS cant able to install packages in final roofs image
> apart from IMAGE_INSTALL .
>

Because an image isn't a package.  RDEPENDS works on packages.  To specify
what goes into an image, use IMAGE_INSTALL and related variables.

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

Re: [yocto] Intelligent global config files setting

[Burton, Ross]

On 9 October 2015 at 08:38, Gilles CARRY  wrote:

> I tried to use ROOTFS_POSTPROCESS_COMMAND in c1.bb and c2.bb but this
> mechanism only seems to work in images recipes. (inherit core-image)
>
>
Use a package postinst to modify the configuration files when the rootfs is
generated?

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

Re: [yocto] kernel-module- prefix for out-of-tree modules mandatory?

[Daniel.]

Thanks!!
Em 09/10/2015 04:25, "Khem Raj"  escreveu:

>
> > On Oct 8, 2015, at 1:29 PM, Daniel.  wrote:
> >
> > Hi all,
> >
> > Is the kernel-module- prefix mandatory for out-of-tree modules
> > compiled inside Yocto? And, This prefix applies to package names or
> > recipe names? Should I rename my recipe file with this prefix or setup
> > PN stuff?
>
> if you inherit module bbclass then the split will happen automatically
> you can name your recipe anything you like, the naming applies to out
> packages only
>
> >
> > Cheers,
> >
> > --
> > "Do or do not. There is no try"
> >  Yoda Master
> > --
> > ___
> > 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] Intelligent global config files setting

[Gilles CARRY]

Yes, this looks good.
I was not aware of this postinst mechanism.
Thanks for the answer.

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, October 09, 2015 12:40 PM
To: Gilles CARRY
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Intelligent global config files setting


On 9 October 2015 at 08:38, Gilles CARRY 
mailto:gilles.ca...@st.com>> wrote:
I tried to use ROOTFS_POSTPROCESS_COMMAND in c1.bb and 
c2.bb but this mechanism only seems to work in images recipes. 
(inherit core-image)

Use a package postinst to modify the configuration files when the rootfs is 
generated?

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

[yocto] Yocto Project Status WW41

[Jolley, Stephen K]

Current Dev Position: YP 2.0 Final (rc1 out of QA and being reviewed.)

Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015


SWAT team rotation: Cristian -> Randy

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Top Bugs to be tackled:

* systemd timeouts in the sanity tests (#7919, #8141, #8142)

* All LSB builds fail sanity testing (#8452)

* wic fails selftest (#8466)


Key Status/Updates:

* Hopefully everyone at ELC-E is having a good time!

* Jethro has branched, current master and jethro are identical and 
master will track jethro until close to release.

* RC1 is out of QA and the results from QA are being reviewed.  RC2 
should be built and go into QA early next week.

* Intermittent systemd, and repeatable LSB and wic failures in sanity 
tests causing failed build runs.

* Reminder:

oWe have renamed YP 1.9 to YP 2.0.

oThe current version that is in development will launch as YP 2.0 in 
October, 2015.

oThe release name for YP 2.0 is 'jethro'.


Key YP 1.9/2.0 Dates:

YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA)

YP 2.0 final Release Target: Before Oct. 30, 2015


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features


Tracking Metrics:

WDD 2055 (last week 2170)

(https://wiki.yoctoproject.org/charts/combo.html)


[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

[yocto] Yocto Project Status WW41 - Updated

[Jolley, Stephen K]

Current Dev Position: YP 2.0 Final (rc1 out of QA and being reviewed.)

Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015


SWAT team rotation: Cristian -> Randy

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Top Bugs to be tackled (2.0 release blockers):

* systemd timeouts in the sanity tests (#7919, #8141, #8142)

* All LSB builds fail sanity testing (#8452)

* wic fails selftest (#8466)


Key Status/Updates:

* Hopefully everyone at ELC-E is having a good time!

* Jethro has branched, current master and jethro are identical and 
master will track jethro for now.

* RC1 is out of QA and the results from QA are being reviewed.  RC2 
will be built and go into QA early next week, assuming fixes become available.

* Intermittent systemd, and repeatable LSB and wic failures in sanity 
tests causing failed build runs are high priority issues which will block 
release.


Reminders:

* We have renamed YP 1.9 to YP 2.0.

* The current version that is in development will launch as YP 2.0 in 
October, 2015.

* The release name for YP 2.0 is 'jethro'.


Key YP 1.9/2.0 Dates:

YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA)

YP 2.0 final Release Target: Before Oct. 30, 2015


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features


Tracking Metrics:

WDD 2055 (last week 2170)

(https://wiki.yoctoproject.org/charts/combo.html)


[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

Re: [yocto] VFAT patent EP 0 618 540

[Robert Berger]

Hi,

On 10/09/2015 11:36 AM, Gorny Krystian wrote:
> Hi,
> 
> I have a question regarding the VFAT patent (EP 0 618 540) owned by
> Microsoft. It’s about common name space for long and short filenames. I
> have read that this patent was canceled by Germany / EU, but it’s still
> available in the US right? So is there a patch/option where we can
> activate to avoid this patent?

I am not a lawyer, but wouldn't it be easier not to use VFAT?
The only reason I would use it, would be because the bootloader of my
SoC would only be able to boot over FAT/FAT32 from a managed flash. A
patch will not help here as well;)

There are rumors that a fix was implemented a long time ago[1] ;)

> 
> Thanks
> 
> Krystian
> 

Regards,

Robert


[1]
http://arstechnica.com/information-technology/2009/07/vfat-linux-patch-could-circumvent-microsofts-patent-claims/

> 
> Legal information:
> Wipotec Wiege- und Positioniersysteme GmbH
> HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner
> 
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in
> error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> 

Since you are concerned about legal issues you might also want to remove
this footer when posting to public lists ;)

> 
> -- 
> 

..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
only): Don't do it yet." - M.A. Jackson (not the singer)

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1


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

Re: [yocto] VFAT patent EP 0 618 540

[Christian Ege]

Hi,
Am 09.10.2015 8:31 nachm. schrieb "Robert Berger" <
gm...@reliableembeddedsystems.com>:
>
> Hi,
>
> On 10/09/2015 11:36 AM, Gorny Krystian wrote:
> > Hi,
> >
> > I have a question regarding the VFAT patent (EP 0 618 540) owned by
> > Microsoft. It’s about common name space for long and short filenames. I
> > have read that this patent was canceled by Germany / EU, but it’s still
> > available in the US right? So is there a patch/option where we can
> > activate to avoid this patent?
>
> I am not a lawyer, but wouldn't it be easier not to use VFAT?
> The only reason I would use it, would be because the bootloader of my
> SoC would only be able to boot over FAT/FAT32 from a managed flash. A
> patch will not help here as well;)
A decent U-Boot can load the kernel from ext4. And I do not know any ROM
loader which needs vfat, except maybe this TI SOCs...

Regards,
Christian
>
> There are rumors that a fix was implemented a long time ago[1] ;)
>
> >
> > Thanks
> >
> > Krystian
> >
>
> Regards,
>
> Robert
>
>
> [1]
>
http://arstechnica.com/information-technology/2009/07/vfat-linux-patch-could-circumvent-microsofts-patent-claims/
>
> >
> > Legal information:
> > Wipotec Wiege- und Positioniersysteme GmbH
> > HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner
> >
> > This e-mail may contain confidential and/or privileged information.
> > If you are not the intended recipient (or have received this e-mail in
> > error)
> > please notify the sender immediately and delete this e-mail. Any
> > unauthorized
> > copying, disclosure or distribution of the material in this e-mail is
> > strictly
> > forbidden.
> >
>
> Since you are concerned about legal issues you might also want to remove
> this footer when posting to public lists ;)
>
> >
> > --
> >
>
> ..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
> only): Don't do it yet." - M.A. Jackson (not the singer)
>
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
>
>
> --
> ___
> 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] VFAT patent EP 0 618 540

[Ayoub Zaki]

TI Socs Boot Rom code can use Vfat but does not necessarly need it as
Bootloaders (spl, u-boot) can be loaded directly  from Raw MMC/eMMC.
Am 09.10.2015 21:59 schrieb "Christian Ege" :

> Hi,
> Am 09.10.2015 8:31 nachm. schrieb "Robert Berger" <
> gm...@reliableembeddedsystems.com>:
> >
> > Hi,
> >
> > On 10/09/2015 11:36 AM, Gorny Krystian wrote:
> > > Hi,
> > >
> > > I have a question regarding the VFAT patent (EP 0 618 540) owned by
> > > Microsoft. It’s about common name space for long and short filenames. I
> > > have read that this patent was canceled by Germany / EU, but it’s still
> > > available in the US right? So is there a patch/option where we can
> > > activate to avoid this patent?
> >
> > I am not a lawyer, but wouldn't it be easier not to use VFAT?
> > The only reason I would use it, would be because the bootloader of my
> > SoC would only be able to boot over FAT/FAT32 from a managed flash. A
> > patch will not help here as well;)
> A decent U-Boot can load the kernel from ext4. And I do not know any ROM
> loader which needs vfat, except maybe this TI SOCs...
>
> Regards,
> Christian
> >
> > There are rumors that a fix was implemented a long time ago[1] ;)
> >
> > >
> > > Thanks
> > >
> > > Krystian
> > >
> >
> > Regards,
> >
> > Robert
> >
> >
> > [1]
> >
> http://arstechnica.com/information-technology/2009/07/vfat-linux-patch-could-circumvent-microsofts-patent-claims/
> >
> > >
> > > Legal information:
> > > Wipotec Wiege- und Positioniersysteme GmbH
> > > HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner
> > >
> > > This e-mail may contain confidential and/or privileged information.
> > > If you are not the intended recipient (or have received this e-mail in
> > > error)
> > > please notify the sender immediately and delete this e-mail. Any
> > > unauthorized
> > > copying, disclosure or distribution of the material in this e-mail is
> > > strictly
> > > forbidden.
> > >
> >
> > Since you are concerned about legal issues you might also want to remove
> > this footer when posting to public lists ;)
> >
> > >
> > > --
> > >
> >
> > ..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
> > only): Don't do it yet." - M.A. Jackson (not the singer)
> >
> > My public pgp key is available,at:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux] [PATCH] libsepol: DEPENDS on flex-native

[Robert Yang]

Fixed when build libsepol-native:
/bin/sh: 1: flex: not found

Signed-off-by: Robert Yang 
---
 recipes-security/selinux/libsepol.inc |2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-security/selinux/libsepol.inc 
b/recipes-security/selinux/libsepol.inc
index b24ed28..a8ee749 100644
--- a/recipes-security/selinux/libsepol.inc
+++ b/recipes-security/selinux/libsepol.inc
@@ -12,4 +12,6 @@ inherit lib_package
 # local ranlib.
 EXTRA_OEMAKE += "RANLIB='$(AR) s'"
 
+DEPENDS += "flex-native"
+
 BBCLASSEXTEND = "native"
-- 
1.7.9.5

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

[yocto] [PATCH][meta-selinux] refpolicy: fix exit code issue of bzip2

[wenzong.fan]

From: Wenzong Fan 

'bzip2 -qt $moudle_name.pp' has different exit codes on different
distributions, for example:

* On Redhat/CentOS/Fedora, OpenSUSE:

  $ bzip2 -qt /tmp/tor.pp
  bzip2: /tmp/tor.pp: bad magic number (file not created by bzip2)
  $ echo $?
  0

This causes install errors:

  unzip2: /path/to/*.pp is not a bzip2 file.
  libsepol.module_package_read_offsets: module package header truncated
  Failed to read policy package

* Ubuntu has fixed it:

  $ bzip2 -qt /tmp/tor.pp
  bzip2: /tmp/tor.pp: bad magic number (file not created by bzip2)
  $ echo $?
  2

The difference involved by '-q' options, remove it would get the bzip2
works consistently. bzip2-native has the same issue, anyway it should
be fixed separately.

Signed-off-by: Wenzong Fan 
---
 recipes-security/refpolicy/refpolicy_common.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/refpolicy/refpolicy_common.inc 
b/recipes-security/refpolicy/refpolicy_common.inc
index de38dfc..5acbf3e 100644
--- a/recipes-security/refpolicy/refpolicy_common.inc
+++ b/recipes-security/refpolicy/refpolicy_common.inc
@@ -84,7 +84,7 @@ prepare_policy_store () {
MOD_DIR=${POL_ACTIVE_MODS}/${MOD_NAME}
mkdir -p ${MOD_DIR}
echo -n "${HLL_TYPE}" > ${MOD_DIR}/lang_ext
-   if ! bzip2 -qt $i 2>/dev/null; then
+   if ! bzip2 -t $i >/dev/null 2>&1; then
${HLL_BIN} $i | bzip2 --stdout > ${MOD_DIR}/cil
bzip2 -f $i && mv -f $i.bz2 $i
else
-- 
1.9.1

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