meta-virtualization.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Changqing Li <changqing.li@eng.windriver.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] [mickledore][master][PATCH] cni: clean dir ${B}/plugins before do_compile
Date: Fri, 27 Oct 2023 03:22:31 +0000	[thread overview]
Message-ID: <ZTss905ikoIx1LhQ@gmail.com> (raw)
In-Reply-To: <20231026114349.57798-1-changqing.li@windriver.com>

merged to mickledore and staged for master.

Bruce

In message: [meta-virtualization] [mickledore][master][PATCH] cni: clean dir ${B}/plugins before do_compile
on 26/10/2023 Changqing Li wrote:

> From: Changqing Li <changqing.li@windriver.com>
> 
> Clean dir ${B}/plugins before do_compile to avoid cni generated binaries
> like /usr/libexec/cni/bridge has wrong dynamic linker path and reports
> error like: /usr/libexec/cni/bridge: no such file or directory".
> 
> Reproduce steps:
> 1. bitbake cni
> 2. enable usrmerge feature in local.conf
> 3. bitbake cni
> 
> After step 2, GOBUILDFLAGS changed,
> "-I /lib64/ld-linux-aarch64.so.1" -> "/usr/lib/ld-linux-aarch64.so.1"
> 
> But "go build" seems only check if the cached packagefile changed, since
> all not changed, the dynamic linker still use the old one, maybe go
> build should improve this.
> 
> Clean dir ${B}/plugins to trigger rebuild of the binaries here.
> 
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
>  recipes-networking/cni/cni_git.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/recipes-networking/cni/cni_git.bb b/recipes-networking/cni/cni_git.bb
> index 71880cd1..a1a31f2d 100644
> --- a/recipes-networking/cni/cni_git.bb
> +++ b/recipes-networking/cni/cni_git.bb
> @@ -53,6 +53,8 @@ do_compile() {
>  	done
>  }
>  
> +do_compile[cleandirs] = "${B}/plugins"
> +
>  do_install() {
>      localbindir="${libexecdir}/cni/"
>  
> -- 
> 2.25.1
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8399): https://lists.yoctoproject.org/g/meta-virtualization/message/8399
> Mute This Topic: https://lists.yoctoproject.org/mt/102197983/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



      reply	other threads:[~2023-10-27  3:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 11:43 [mickledore][master][PATCH] cni: clean dir ${B}/plugins before do_compile changqing.li
2023-10-27  3:22 ` Bruce Ashfield [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=ZTss905ikoIx1LhQ@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=changqing.li@eng.windriver.com \
    --cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).