All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Ash Charles <ashcharles@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [Patch v3] eject: copy po subdirectory for out-of-tree build
Date: Fri, 13 Jun 2014 16:47:46 +0200	[thread overview]
Message-ID: <20140613144746.GJ2428@jama> (raw)
In-Reply-To: <CAK8F28kOVF4uwefMHoFmjv8TLfhARRbbvASQyTC4avWfdWf3uw@mail.gmail.com>

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

On Fri, Jun 13, 2014 at 06:57:54AM -0700, Ash Charles wrote:
> Any chance this is getting built with autotools-brokensep still in place?

Yes, that could be it, I'll remove eject from my big autotools-broken
sep, but can we make it compatible with B=S as well? That's what commit
message suggests.

> On Jun 13, 2014 4:40 AM, "Martin Jansa" <martin.jansa@gmail.com> wrote:
> 
> > On Tue, Jun 10, 2014 at 11:18:02AM -0700, Ash Charles wrote:
> > > The po subdirectory found on the VPATH for an out-of-tree build so we
> > > copy it over. See [1] for discussion.
> > >
> > > [1]
> > http://lists.openembedded.org/pipermail/openembedded-devel/2014-May/096052.html
> > >
> > > v3: only create and populate po/ if it doesn't already exist
> >
> > ^ this doesn't match with patch and it still fails:
> >
> > ERROR: Function failed: do_compile (log file is located at
> > /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/temp/log.do_compile.31092)
> > ERROR: Logfile of failure stored in:
> > /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/temp/log.do_compile.31092
> > Log data follows:
> > | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
> > 'bit-64', 'x86_64-linux', 'common']
> > | DEBUG: Executing shell function do_compile
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/CVS'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/CVS'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/Makefile'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/Makefile'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/cs_CZ.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/cs_CZ.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/de_DE.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/de_DE.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/eject.pot'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/eject.pot'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/es_ES.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/es_ES.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/fr_FR.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/fr_FR.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/ja_JP.eucJP.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/ja_JP.eucJP.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/pt_BR.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/pt_BR.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/tr_TR.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/tr_TR.po'
> > are the same file
> > | cp:
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/zh_TW.UTF-8.po'
> > and
> > `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/eject/po/zh_TW.UTF-8.po'
> > are the same file
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_compile (log file is located at
> > /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/eject/2.1.5-r1/temp/log.do_compile.31092)
> > NOTE: recipe eject-2.1.5-r1: task do_compile: Failed
> > ERROR: Task 21543
> > (/home/jenkins/oe/shr-core-branches/shr-core/meta-openembedded/meta-oe/recipes-support/eject/
> > eject_2.1.5.bb, do_compile) failed with exit code '1'
> >
> > > Signed-off-by: Ash Charles <ashcharles@gmail.com>
> > > Reviewed-by: Otavio Salvador <otavio@ossystems.com.br>
> > > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > > ---
> > >  meta-oe/recipes-support/eject/eject_2.1.5.bb | 6 ++++++
> > >  1 file changed, 6 insertions(+)
> > >
> > > 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 c47c653..a71d83f 100644
> > > --- a/meta-oe/recipes-support/eject/eject_2.1.5.bb
> > > +++ b/meta-oe/recipes-support/eject/eject_2.1.5.bb
> > > @@ -16,6 +16,12 @@ S = "${WORKDIR}/${BPN}"
> > >
> > >  PR = "r1"
> > >
> > > +do_compile_prepend() {
> > > +    # PO subdir must be in build directory
> > > +    mkdir -p ${B}/po
> > > +    cp -r ${S}/po/* ${B}/po/
> > > +}
> > > +
> > >  ALTERNATIVE_${PN} = "volname eject"
> > >  ALTERNATIVE_LINK_NAME[volname] = "${bindir}/volname"
> > >  ALTERNATIVE_LINK_NAME[eject] = "${bindir}/eject"
> > > --
> > > 1.8.3.2
> > >
> >
> > --
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> >

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

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

  reply	other threads:[~2014-06-13 14:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 19:27 [meta-oe][PATCH] eject: link po subdirectory for out-of-tree build Ash Charles
2014-05-26 20:31 ` Otavio Salvador
2014-05-26 22:09   ` Ash Charles
2014-05-27  0:46     ` Ash Charles
2014-05-27  2:43       ` Otavio Salvador
2014-05-27  9:18 ` Martin Jansa
2014-05-27 15:15   ` Ash Charles
2014-05-27 15:32     ` Otavio Salvador
2014-05-27 16:43       ` [meta-oe][PATCH v2] eject: copy " Ash Charles
2014-05-27 17:41         ` Otavio Salvador
2014-05-27 16:44       ` [meta-oe][PATCH] eject: link " Ash Charles
2014-05-28 19:43       ` Khem Raj
2014-06-10 11:26 ` Martin Jansa
2014-06-10 18:18   ` [Patch v3] eject: copy " Ash Charles
2014-06-13 11:40     ` Martin Jansa
2014-06-13 13:57       ` Ash Charles
2014-06-13 14:47         ` Martin Jansa [this message]
2014-06-13 20:45           ` [Patch v4] " Ash Charles

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=20140613144746.GJ2428@jama \
    --to=martin.jansa@gmail.com \
    --cc=ashcharles@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 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.