public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Changqing Li" <changqing.li@windriver.com>
To: Jacob Kroon <jacob.kroon@gmail.com>,
	openembedded-core@lists.openembedded.org,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH] iproute2.inc: clean .o before do_configure
Date: Fri, 8 May 2020 12:02:42 +0800	[thread overview]
Message-ID: <9f9edaaf-18fc-78e7-f7d2-7dc12c6356f7@windriver.com> (raw)
In-Reply-To: <21a173ab-7496-d134-21a6-a49fe4fd46c5@gmail.com>


On 5/7/20 2:19 PM, Jacob Kroon wrote:
> On 5/7/20 8:10 AM, Changqing Li wrote:
>> On 5/7/20 1:56 PM, Jacob Kroon wrote:
>>> On 5/7/20 4:05 AM, Changqing Li wrote:
>>>> From: Changqing Li <changqing.li@windriver.com>
>>>>
>>>> Reproduce steps:
>>>> 1. add 'DISTRO_FEATURES_append = ' usrmerge'' in local.conf
>>>> 2. bitbake iproute2
>>>> 3. remove 'DISTRO_FEATURES_append = ' usrmerge'' from local.conf
>>>> 4. bitbake iproute2
>>>>
>>>> In step4, since CLEANBROKEN is set, files generated in step2 is not
>>>> cleaned and rebuilded. Check after step4:
>>>>
>>>> file /sbin/ip.iproute2
>>>> /sbin/ip.iproute2: ELF 64-bit LSB pie executable, x86-64, version 1
>>>> (SYSV), dynamically linked, interpreter 
>>>> /usr/lib64/ld-linux-x86-64.so.2,
>>>>
>>>> interpreter path is wrong, it should be /lib64/ld-linux-x86-64.so.2
>>>>
>>>> This will make run ip.iproute2 report error:
>>>> -sh: /sbin/ip.iproute2: No such file or directory
>>>>
>>>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
>>>> ---
>>>>   meta/recipes-connectivity/iproute2/iproute2.inc | 4 ++++
>>>>   1 file changed, 4 insertions(+)
>>>>
>>>
>>> Isn't this a general problem, and not specific to just iproute2 ?
>>
>> For  those recipe ${B} != ${S} ,  ${B} will be cleaned,  will not 
>> have this problem.
>>
>> and by default, CLEANBROKEN is not set,  make clean will be executed.
>>
>> but for this specific recipe,  both condition not matched.
>>
>>
>
> btrfs-tools inherits autotools-brokensep and sets CLEANBROKEN = "1", 
> will it also require a similar fix ?

In theory, btrfs-tools and other recipes like this will met similar 
problem.


But I tested on btrfs-tools, it don't met problem even without clean, 
since some dependency changed, so

binary btrfs also recompiled. so this is also related to respective 
makefile.


And your suggestion to make it commons also make sense,  in this way,  
we need to

handle condition (${B} and ${S} is same,and CLEANBROKEN = "1")

in base.bbclass and autotools-brokensep.bbclass.   But one problem here 
is  that

we have kinds of recipes,  not all Intermediate file are *.o, how to 
handle this, any suggestion?

or still handle this in seperate recipes?




      reply	other threads:[~2020-05-08  4:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  2:05 [PATCH] iproute2.inc: clean .o before do_configure Changqing Li
2020-05-07  5:56 ` [OE-core] " Jacob Kroon
2020-05-07  6:10   ` Changqing Li
2020-05-07  6:19     ` Jacob Kroon
2020-05-08  4:02       ` Changqing Li [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=9f9edaaf-18fc-78e7-f7d2-7dc12c6356f7@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=jacob.kroon@gmail.com \
    --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