Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	openembedded-devel@lists.openembedded.org
Cc: otavio@ossystems.com.br
Subject: Re: [PATCH 7/7] krb5: Fix warning.
Date: Tue, 9 Feb 2016 12:27:40 -0800	[thread overview]
Message-ID: <56BA4BBC.6030800@gmail.com> (raw)
In-Reply-To: <20160209180833.GA2608@jama>



On 02/09/2016 10:08 AM, Martin Jansa wrote:
> On Sun, Feb 07, 2016 at 01:11:59PM -0800, Armin Kuster wrote:
>> From: Armin Kuster <akuster@mvista.com>
>>
>> WARNING: /tmp/work/armv5e-poky-linux-gnueabi/krb5/1.12.2-r0/krb5-1.12.2/src/ ('S') doesn't exist, please set 'S' to a proper value
>>
>> remove extra "/"
> 
> This patch isn't in master and master still has trailing /, why is this
> needed for fido only?

I only saw it occur in fido.

- armin
> 
>>
>> Signed-off-by: Armin Kuster <akuster@mvista.com>
>> ---
>>  meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb b/meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb
>> index c492496..c19fffb 100644
>> --- a/meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb
>> +++ b/meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb
>> @@ -33,7 +33,7 @@ SRC_URI = "http://web.mit.edu/kerberos/dist/${BPN}/${SHRT_VER}/${BP}-signed.tar
>>  SRC_URI[md5sum] = "357f1312b7720a0a591e22db0f7829fe"
>>  SRC_URI[sha256sum] = "09bd180107b5c2b3b7378c57c023fb02a103d4cac39d6f2dd600275d7a4f3744"
>>  
>> -S = "${WORKDIR}/${BP}/src/"
>> +S = "${WORKDIR}/${BP}/src"
>>  
>>  PACKAGECONFIG ??= "openssl"
>>  PACKAGECONFIG[libedit] = "--with-libedit,--without-libedit,libedit"
>> -- 
>> 2.3.5
>>
>> -- 
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> 


  reply	other threads:[~2016-02-09 20:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 21:11 [PATCH 0/7][fido] Pull request Armin Kuster
2016-02-07 21:11 ` [PATCH 1/7] squid: serveral missing security fixes Armin Kuster
2016-02-07 21:11 ` [PATCH 2/7] ntp: fix rpath QA issue Armin Kuster
2016-02-07 21:11 ` [PATCH 3/7] ntp: upgrade 4.2.8p3 -> 4.2.8p4 Armin Kuster
2016-02-07 21:11 ` [PATCH 4/7] php: Security fix CVE-2015-7803 Armin Kuster
2016-02-07 21:11 ` [PATCH 5/7] php: Security fix CVE-2015-7804 Armin Kuster
2016-02-07 21:11 ` [PATCH 6/7] php: Security fix CVE-2016-1903 Armin Kuster
2016-02-07 21:11 ` [PATCH 7/7] krb5: Fix warning Armin Kuster
2016-02-09 18:08   ` Martin Jansa
2016-02-09 20:27     ` akuster808 [this message]
2016-02-09 21:41       ` Khem Raj
2016-02-09 23:33         ` akuster808

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=56BA4BBC.6030800@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox