public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>,
	Christopher Larson <clarson@kergoth.com>,
	Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: fido -> jethro switching problem
Date: Fri, 15 Jan 2016 13:06:09 +0000	[thread overview]
Message-ID: <1452863169.28375.161.camel@linuxfoundation.org> (raw)
In-Reply-To: <5698E002.5090800@dresearch-fe.de>

On Fri, 2016-01-15 at 13:03 +0100, Steffen Sledz wrote:
> Hi all,
> 
> for our internal development we use the Angstrom distro with some
> additional layers. Now we try to switch from fido to jethro branches
> and hit a problem where we are overchallenged.
> 
> Our local.conf contains
> 
>   DISTRO_FEATURES_remove = "x11 wayland"
> 
> what results in

The error you pasted means that your setup has some kind of circular
override references in it.

Am I correct in understanding that you hit the same error regardless of
the above line or not? If so, that means the problem is probably
elsewhere in your configuration.

As an example of what would cause this kind of issue:

OVERRIDES = "${VAR1}:${VAR2}"

VAR1 = "VAL1"VAR2 = "VAL2"
VAR2_VAL2 = "VAL1"

So bitbake would try and expand OVERRIDES and get "VAL1:VAL2", that
would change the value of VAR2 to VAL1, making overrides "VAL1:VAL1",
hence VAR2 now becomes VAL2, so OVERRIDES changes and so on.

Rather than infinitely loop, the code exits. There isn't code in there
which tries to figure out the circular dependency path since that is
rather complicated and there can be multiple levels of indirection
rather than just the single level above.

You probably need to track down which OVERRIDES value is causing the
problem, then work through the usages of it to find the problem, or
instrument the code to see which values are changing and causing the
instability.

Cheers,

Richard











  reply	other threads:[~2016-01-15 13:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 12:03 fido -> jethro switching problem Steffen Sledz
2016-01-15 13:06 ` Richard Purdie [this message]
2016-01-15 13:24   ` Steffen Sledz
2016-01-15 14:26     ` Steffen Sledz
2016-01-15 14:29       ` Koen Kooi
2016-01-18  8:28         ` Steffen Sledz
2016-01-18  8:41           ` Koen Kooi
2016-01-18 10:10             ` Steffen Sledz
2016-01-18 10:19               ` Koen Kooi
2016-01-18 11:55         ` Steffen Sledz
2016-01-18 12:25           ` Koen Kooi
2016-01-15 14:29       ` 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=1452863169.28375.161.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=clarson@kergoth.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sledz@dresearch-fe.de \
    /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