From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Alexander Kanavin : remake: update to 4.1+dbg-1.1
Date: Tue, 15 Mar 2016 16:18:34 +0000 [thread overview]
Message-ID: <1458058714.7615.3.camel@linuxfoundation.org> (raw)
In-Reply-To: <56E82EBA.10008@linux.intel.com>
On Tue, 2016-03-15 at 17:48 +0200, Alexander Kanavin wrote:
> On 03/10/2016 11:01 PM, Richard Purdie wrote:
>
> > > Fails to build after make was built. Shouldn't it be at least
> > > blacklisted
> > > by default so that potential user will need to explicitly decide
> > > between
> > > make and remake (and unmerge the other one from sysroot first)?
> >
> > I think (but can't remember for sure) that if you make both recipes
> > PROVIDE virtual/make, the right things should happen?
>
> remake recipe already includes this line:
> PROVIDES += "make"
>
> And we also have this in distro config:
> PREFERRED_PROVIDER_make ?= "make"
>
> And yet, if you try to build remake after make, the right thing
> (clearing out the sysroot files installed by make) does not happen.
> Any
> suggestions?
I think virtual/make would make more "magic" happen...
I think "make" would have made some of that happen though, hmm.
Cheers,
Richard
prev parent reply other threads:[~2016-03-15 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150904153710.BBCFA50436@opal.openembedded.org>
2016-03-10 11:58 ` [oe-commits] Alexander Kanavin : remake: update to 4.1+dbg-1.1 Martin Jansa
2016-03-10 21:01 ` Richard Purdie
2016-03-15 15:48 ` Alexander Kanavin
2016-03-15 16:18 ` Richard Purdie [this message]
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=1458058714.7615.3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@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