From: Joe MacDonald <joe@deserted.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking] [PATCH] traceroute: filter-out patches dir
Date: Wed, 12 Feb 2014 19:59:26 -0500 [thread overview]
Message-ID: <20140213005923.GE23405@deserted.net> (raw)
In-Reply-To: <CAP9ODKr5h8uX9yp+b9n8MpniGGosZ+MW_YEk9dKPR8QHj-XO7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
[Re: [oe] [meta-networking] [PATCH] traceroute: filter-out patches dir] On 14.01.22 (Wed 12:21) Otavio Salvador wrote:
> On Mon, Jan 20, 2014 at 10:52 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
> > The $(subdirs) contains all the dirs under the ${B}, and this one:
> >
> > do_unpack[cleandirs] = "${S}/patches"
> >
> > will create a "patches" dir, then there will be compile errors, filter
> > out the patches will fix the problem.
> >
> > Note: poky doesn't have this problem since it separates the ${S} and
> > ${B}
> >
> > Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>
> Couldn't we change it for OE-Core as well? So we avoid having to patch
> the build system.
That seems sensible. I've not seen any follow-up on this, so I'm going
to drop this patch and assume this is a change being done in OE-Core (if
it hasn't already been done there).
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-02-13 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 12:52 [meta-networking] [PATCH] traceroute: filter-out patches dir Robert Yang
2014-01-22 14:21 ` Otavio Salvador
2014-02-13 0:59 ` Joe MacDonald [this message]
2014-02-13 3:03 ` Robert Yang
2014-02-13 10:40 ` Otavio Salvador
2014-02-14 3:29 ` Joe MacDonald
2014-02-14 6:32 ` Robert Yang
2014-03-18 9:24 ` Robert Yang
2014-03-27 20:28 ` Joe MacDonald
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=20140213005923.GE23405@deserted.net \
--to=joe@deserted.net \
--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