Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] eject: Fix B != S builds
Date: Tue, 24 Jun 2014 01:58:59 +0200	[thread overview]
Message-ID: <20140623235859.GK2437@jama> (raw)
In-Reply-To: <1403553432.2104.112.camel@ted>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

On Mon, Jun 23, 2014 at 08:57:12PM +0100, Richard Purdie wrote:
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> 
> diff --git a/meta-oe/recipes-support/eject/eject_2.1.5.bb b/meta-oe/recipes-support/eject/eject_2.1.5.bb
> index 9534577..6cb31a7 100644
> --- a/meta-oe/recipes-support/eject/eject_2.1.5.bb
> +++ b/meta-oe/recipes-support/eject/eject_2.1.5.bb
> @@ -9,6 +9,11 @@ SRC_URI = "http://sources.openembedded.org/${BP}.tar.gz \
>             file://eject-2.1.5-error-return.patch \
>  "
>  
> +do_compile_prepend () {
> +    mkdir -p ${B}/po
> +    cp -r ${S}/po/* ${B}/po/
> +}

Wasn't this fixed already? I've seen it in your big patch, but the same
logic is applied in newer master already.

> +
>  SRC_URI[md5sum] = "b96a6d4263122f1711db12701d79f738"
>  SRC_URI[sha256sum] = "ef9f7906484cfde4ba223b2682a37058f9a3c7d3bb1adda7a34a67402e2ffe55"
>  
> 
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-06-23 23:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 19:57 [meta-oe][PATCH] eject: Fix B != S builds Richard Purdie
2014-06-23 23:58 ` Martin Jansa [this message]
2014-06-24  7:03   ` Richard Purdie

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=20140623235859.GK2437@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox