From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [oe] kernel.bbclass: Fix do_shared_workdir task ordering
Date: Wed, 14 Oct 2015 12:30:33 -0700 [thread overview]
Message-ID: <20151014193033.GD3552@dent.vctlabs.com> (raw)
In-Reply-To: <1439220090-3305-1-git-send-email-s.mueller-klieser@phytec.de>
http://patchwork.openembedded.org/patch/99875/
Apparently this patch is still not in master, and I just ran across the
problem with an externally built module (omaplfb from omap3-sgx-modules)
in meta-ti layer.
What's the plan for getting a correct Module.symver into shared_workdir
for external modules to build against? Above patch, or does someone have
an even better idea?
next prev parent reply other threads:[~2015-10-14 19:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 15:21 [PATCH] kernel.bbclass: Fix do_shared_workdir task ordering Stefan Müller-Klieser
2015-08-11 3:23 ` Bruce Ashfield
2015-08-11 12:47 ` Otavio Salvador
2015-08-11 13:06 ` Bruce Ashfield
2015-08-11 13:11 ` Bruce Ashfield
2015-08-11 14:25 ` Stefan Müller-Klieser
2015-08-11 15:10 ` Bruce Ashfield
2015-10-14 18:35 ` S. Lockwood-Childs
2015-10-14 18:22 ` Martin Jansa
2015-10-14 19:30 ` S. Lockwood-Childs [this message]
2015-10-14 19:48 ` [OE-core] " Bruce Ashfield
2015-10-14 19:48 ` [oe] " Bruce Ashfield
2015-11-10 9:33 ` [OE-core] " Jens Rehsack
2015-11-10 9:33 ` [oe] " Jens Rehsack
2015-11-11 2:01 ` [OE-core] " Bruce Ashfield
2015-11-11 2:01 ` [oe] " Bruce Ashfield
2015-11-11 9:00 ` [OE-core] " Jens Rehsack
2015-11-11 9:00 ` [oe] " Jens Rehsack
2015-11-11 12:49 ` [OE-core] " Bruce Ashfield
2015-11-11 12:49 ` [oe] " Bruce Ashfield
2015-11-11 14:59 ` [OE-core] " Jens Rehsack
2015-11-11 14:59 ` [oe] " Jens Rehsack
2015-11-11 22:59 ` [OE-core] " Bruce Ashfield
2015-11-11 22:59 ` [oe] " Bruce Ashfield
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=20151014193033.GD3552@dent.vctlabs.com \
--to=sjl@vctlabs.com \
--cc=denys@ti.com \
--cc=openembedded-core@lists.openembedded.org \
--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.