From: Mike Looijmans <mike.looijmans@topic.nl>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Problem with RDEPENDS in multimachine builds for allarch packages
Date: Tue, 27 Oct 2015 09:58:18 +0100 [thread overview]
Message-ID: <562F3CAA.6040401@topic.nl> (raw)
In-Reply-To: <1445934977.4521.11.camel@linuxfoundation.org>
On 27-10-15 09:36, Richard Purdie wrote:
> On Tue, 2015-10-27 at 09:30 +0100, Mike Looijmans wrote:
>> On 26-10-15 16:13, Sergey 'Jin' Bostandzhyan wrote:
>>> Hi,
>>>
>>> I recently ran into a problem that I described here:
>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8578 and while debugging
>>> this issue an other problem came to light.
>>>
>>> I have a multimachine configuration (armv5/imx6) and the same distro for both
>>> of them (poky 2.0 RC based).
>>>
>>> I have some allarch packages which have no DEPENDS, however which have an
>>> RDEPENDS_${PN} setting.
>>>
>>> I can see that even though there were no changes to the recipe itself and
>>> also no changes to the recipes listed in RDEPENDS, my recipe still gets
>>> rebuilt each time.
>>>
>>> What we tried:
>>>
>>> <bluelightning> so cleansstate the recipe, change machine, cleansstate again,
>>> then build it, then change machine, build it again and note
>>> the first task that executes
>>>
>>> The logs for these steps, one with RDEPENDS and one without are at the end of
>>> this mail. I can see that with present RDEPENDS "real" tasks get executed
>>> even though no changes occured in the recipe; this is not the case when I
>>> drop RDEPENDS.
>>>
>>> Is this a bug or is this just something that needs to be documented?
>>
>> I think it's the same problem as described here:
>> http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/70070/focus=70072
>>
>>> What is the "desired" behaviour?
>>
>> Apparently, this needless rebuilding is "desired".
>
> Its more that we can't tell the difference between a case where it is
> needless and a case where it is no. The system therefore rebuilds as if
> it didn't, there would be cases where it should have rebuilt and did
> not.
But that would not solve any issue at all.
Whatever package got built last will end up in the feed, under the "all"
architecture. So if machine X and Y have different versions of some package P,
and the build for Y ran last, machine X will still install Y's version of P.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
Visit us at : Aerospace Electrical Systems Expo Europe which will be held from 17.11.2015 till 19.11.2015, Findorffstrasse 101 Bremen, Germany, Hall 5, stand number C65
http://www.aesexpo.eu
prev parent reply other threads:[~2015-10-27 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 15:13 Problem with RDEPENDS in multimachine builds for allarch packages Sergey 'Jin' Bostandzhyan
2015-10-26 16:13 ` Christopher Larson
2015-10-26 16:26 ` Sergey 'Jin' Bostandzhyan
2015-10-26 18:20 ` Martin Jansa
2015-10-27 8:30 ` Mike Looijmans
2015-10-27 8:36 ` Richard Purdie
2015-10-27 8:58 ` Mike Looijmans [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=562F3CAA.6040401@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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