From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org,
Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Alexander Kanavin : remake: update to 4.1+dbg-1.1
Date: Thu, 10 Mar 2016 21:01:45 +0000 [thread overview]
Message-ID: <1457643705.2804.229.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160310115851.GD2573@jama>
On Thu, 2016-03-10 at 12:58 +0100, Martin Jansa wrote:
> On Fri, Sep 04, 2015 at 03:37:10PM +0000, git@git.openembedded.org wr
> ote:
> > Module: openembedded-core.git
> > Branch: master
> > Commit: fb781bee39e312eef1d89c2d7f5ab27e8da1ee32
> > URL: http://git.openembedded.org/?p=openembedded-core.git&a=comm
> > it;h=fb781bee39e312eef1d89c2d7f5ab27e8da1ee32
> >
> > Author: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> > Date: Thu Sep 3 18:34:18 2015 +0300
> >
> > remake: update to 4.1+dbg-1.1
> >
> > remake-remove-errors-about-colophon-and-cygnus-comma.patch has been
> > merged upstream
>
> 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?
Cheers,
Richard
next prev parent reply other threads:[~2016-03-10 21:01 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 [this message]
2016-03-15 15:48 ` Alexander Kanavin
2016-03-15 16:18 ` 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=1457643705.2804.229.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