All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@googlemail.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Does recipe specific sysrooot (or whatelse in current oe) break native dependencies?
Date: Mon, 13 Feb 2017 16:45:25 +0100	[thread overview]
Message-ID: <CALbNGRQns-G9XOtS8wGetnAAYVv7Z+F+2h3rLQ2XxgSiSBwHWQ@mail.gmail.com> (raw)
In-Reply-To: <1486999455.13854.241.camel@intel.com>

On Mon, Feb 13, 2017 at 4:24 PM, Patrick Ohly <patrick.ohly@intel.com> wrote:
> On Mon, 2017-02-13 at 15:36 +0100, Martin Jansa wrote:
>> Hi Andreas,
>>
>>
>> I think it's feature which was already there, but almost never
>> triggered (even in test-dependencies.sh tests), but with RSS it fails
>> reliably.
>>
>>
>> See:
>> http://lists.openembedded.org/pipermail/openembedded-core/2016-July/124435.html

Richard wrote
| What it does mean is that any recipe needing a -native recipe to build
| should list it in DEPENDS directly, not rely on other dependencies to
| pull it in for them. This applies to pkgconfig-native, intltool-native
| and also to wayland-native.

This answers my question and leaves me unhappy - I am out for a while..

Andreas


  parent reply	other threads:[~2017-02-13 15:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  0:26 Does recipe specific sysrooot (or whatelse in current oe) break native dependencies? Andreas Müller
2017-02-13 13:47 ` Andreas Müller
2017-02-13 14:36   ` Martin Jansa
2017-02-13 15:15     ` Andreas Müller
2017-02-13 15:24     ` Patrick Ohly
2017-02-13 15:32       ` Martin Jansa
2017-02-13 15:37         ` Patrick Ohly
2017-02-13 15:52           ` Max Krummenacher
2017-02-13 15:45       ` Andreas Müller [this message]
2017-02-13 18:05         ` Richard Purdie
2017-02-13 18:17           ` Andreas Müller
2017-03-05  0:55           ` Andreas Müller
2017-02-13 17:03       ` Patrick Ohly
2017-02-13 17:06         ` Patrick Ohly
2017-02-14 10:26         ` Patrick Ohly
2017-02-19 22:26           ` Richard Purdie
2017-02-20 14:14             ` Patrick Ohly

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=CALbNGRQns-G9XOtS8wGetnAAYVv7Z+F+2h3rLQ2XxgSiSBwHWQ@mail.gmail.com \
    --to=schnitzeltony@googlemail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patrick.ohly@intel.com \
    /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.