All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: zangrc <zangrc.fnst@fujitsu.com>
Cc: meta-virtualization@yoctoproject.org
Subject: Re: [meta-virtualization] [PATCH] criu: skip QA checks textrel
Date: Wed, 7 Jul 2021 15:43:34 -0400	[thread overview]
Message-ID: <20210707194334.GC55535@gmail.com> (raw)
In-Reply-To: <1625638084-8262-1-git-send-email-zangrc.fnst@fujitsu.com>

Were these warnings always there ? or has it been something introduced
by recent uprevs of crui ?

Bruce


In message: [meta-virtualization] [PATCH] criu: skip QA checks textrel
on 07/07/2021 zangrc wrote:

> WARNING: criu-3.14+gitAUTOINC+e49ce513c8-r0 do_package_qa: QA Issue: criu: ELF binary /usr/sbin/criu has relocations in .text [textrel]
> 
> Signed-off-by: Zang Ruochen <zangrc.fnst@fujitsu.com>
> ---
>  recipes-containers/criu/criu_git.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/recipes-containers/criu/criu_git.bb b/recipes-containers/criu/criu_git.bb
> index febf81e..6342620 100644
> --- a/recipes-containers/criu/criu_git.bb
> +++ b/recipes-containers/criu/criu_git.bb
> @@ -22,6 +22,8 @@ SRC_URI = "git://github.com/checkpoint-restore/criu.git;branch=criu-dev \
>             file://lib-Makefile-overwrite-install-lib-to-allow-multiarc.patch \
>            "
>  
> +INSANE_SKIP_${PN} += "textrel"
> +
>  COMPATIBLE_HOST = "(x86_64|arm|aarch64).*-linux"
>  
>  DEPENDS += "libnl libcap protobuf-c-native protobuf-c util-linux-native libbsd libnet"
> -- 
> 2.25.1
> 

> 
> 
> 


  reply	other threads:[~2021-07-07 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07  6:08 [meta-virtualization] [PATCH] criu: skip QA checks textrel zangrc
2021-07-07 19:43 ` Bruce Ashfield [this message]
2021-07-08  2:48   ` zangrc
     [not found] ` <168F99BB02677739.30794@lists.yoctoproject.org>
2021-07-07 19:44   ` Bruce Ashfield

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=20210707194334.GC55535@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=meta-virtualization@yoctoproject.org \
    --cc=zangrc.fnst@fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.