public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Jacob Kroon" <jacob.kroon@gmail.com>
To: Changqing Li <changqing.li@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] iproute2.inc: clean .o before do_configure
Date: Thu, 7 May 2020 07:56:15 +0200	[thread overview]
Message-ID: <015c4b93-6ca1-0668-0c1d-2a3150c65a38@gmail.com> (raw)
In-Reply-To: <1588817159-434433-1-git-send-email-changqing.li@windriver.com>

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 ?

  reply	other threads:[~2020-05-07  5:56 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 ` Jacob Kroon [this message]
2020-05-07  6:10   ` [OE-core] " Changqing Li
2020-05-07  6:19     ` Jacob Kroon
2020-05-08  4:02       ` Changqing Li

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=015c4b93-6ca1-0668-0c1d-2a3150c65a38@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=changqing.li@windriver.com \
    --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