All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: Mark Hatle <mark.hatle@windriver.com>, <yocto@yoctoproject.org>
Subject: Re: [meta-selinux][PATCH] setools: Add bison and flex to DEPENDS
Date: Fri, 23 May 2014 09:50:05 +0800	[thread overview]
Message-ID: <537EA94D.5010509@windriver.com> (raw)
In-Reply-To: <537E01FE.9010804@windriver.com>


On 05/22/2014 09:56 PM, Mark Hatle wrote:
> On 5/21/14, 10:28 PM, Chong Lu wrote:
>> Avoid policy_scan.c: No such file or directory
>>
>> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
>> ---
>>   recipes-security/setools/setools_3.3.8.bb |    2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/recipes-security/setools/setools_3.3.8.bb 
>> b/recipes-security/setools/setools_3.3.8.bb
>> index 1e95a60..3425064 100644
>> --- a/recipes-security/setools/setools_3.3.8.bb
>> +++ b/recipes-security/setools/setools_3.3.8.bb
>> @@ -27,7 +27,7 @@ LIC_FILES_CHKSUM = 
>> "file://${S}/COPYING;md5=26035c503c68ae1098177934ac0cc795 \
>> file://${S}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe \
>> file://${S}/COPYING.LGPL;md5=fbc093901857fcd118f065f900982c24"
>>
>> -DEPENDS += "python libsepol libselinux libxml2"
>> +DEPENDS += "bison flex python libsepol libselinux libxml2"
>
> I suspect the above is incorrect, shouldn't this be "bison-native" (or 
> "bison-native bison")?
>
> During cross compilation, it's the native bison that produces the .c 
> code.
>
> --Mark
Yes, you are right. This should be bison-native and flex-native.
I will resend V2.

Best Regards
Chong
>
>>
>>   PACKAGE_BEFORE_PN += "${PN}-libs"
>>
>>
>



      reply	other threads:[~2014-05-23  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22  3:28 [meta-selinux][PATCH] setools: Add bison and flex to DEPENDS Chong Lu
2014-05-22 13:56 ` Mark Hatle
2014-05-23  1:50   ` Chong Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537EA94D.5010509@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=mark.hatle@windriver.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.