meta-virtualization.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Qi" <Qi.Chen@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "meta-virtualization@lists.yoctoproject.org"
	<meta-virtualization@lists.yoctoproject.org>
Subject: RE: [meta-virtualization][master][kirkstone][PATCH 2/3] docker-distribution: fix build error on new hosts
Date: Fri, 10 Jun 2022 13:58:34 +0000	[thread overview]
Message-ID: <CO6PR11MB56025C31C487BD7ECF4EA2C1EDA69@CO6PR11MB5602.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CADkTA4OVCWoKY3TLAtAqzkGGUgsJt_Dgh=iHpwnDJdugWDD=tg@mail.gmail.com>

Hi Bruce,

Got it. I'll adjust these CGO_XXX settings and send out V2 next week.

Regards,
Qi

-----Original Message-----
From: Bruce Ashfield <bruce.ashfield@gmail.com> 
Sent: Friday, June 10, 2022 9:01 PM
To: Chen, Qi <Qi.Chen@windriver.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][master][kirkstone][PATCH 2/3] docker-distribution: fix build error on new hosts

On Fri, Jun 10, 2022 at 12:21 AM Chen Qi <Qi.Chen@windriver.com> wrote:
>
> The CGO_CFLAGS and other related variables have already been set 
> appropriately by the go.bbclass in oe-core. Setting them in this 
> recipe is not only unncessary but also error prone.
>
> For example CGO_CFLAGS is set to use BUILDSDK_CFLAGS, and this is 
> incorrect. We need target flags instead of SDK related flags. Such 
> setting happens to work for some hosts. However, when building on 
> newer hosts, we get QA error like below:
>
>   ERROR: docker-distribution-v2.7.1-r0 do_package_qa:
>   QA Issue: /usr/sbin/registry contained in package docker-registry requires
>   libc.so.6(GLIBC_2.34)(64bit), but no providers found in 
> RDEPENDS_docker-registry? [file-rdeps]
>
> The above error was found on hardknott on host Fedora 35.
> Tracking down the error and I found it's using host stuff which is 
> likely to be caused by using incorrect CGO_CFLAGS. As the master 
> branch is using the same settings, it has the same issue.

And as I mentioned, feel free to adjust the flags and explicit settings, but I won't be dropping them.

I've been through 6 years of getting these recipes working, and continually being broken by changes in the core classes, so I'm not going to drop the explicit settings.

Bruce

>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>  .../docker-distribution/docker-distribution_git.bb       | 9 ---------
>  1 file changed, 9 deletions(-)
>
> diff --git 
> a/recipes-containers/docker-distribution/docker-distribution_git.bb 
> b/recipes-containers/docker-distribution/docker-distribution_git.bb
> index 1d074bf3..679bcf8b 100644
> --- 
> a/recipes-containers/docker-distribution/docker-distribution_git.bb
> +++ b/recipes-containers/docker-distribution/docker-distribution_git.b
> +++ b
> @@ -23,17 +23,8 @@ inherit go systemd
>  EXTRA_OEMAKE="BUILDTAGS=''"
>
>  do_compile() {
> -       export GOARCH="${TARGET_GOARCH}"
>         export GOPATH="${WORKDIR}/git/"
> -       export GOROOT="${STAGING_LIBDIR_NATIVE}/${TARGET_SYS}/go"
> -       # Pass the needed cflags/ldflags so that cgo
> -       # can find the needed headers files and libraries
> -       export CGO_ENABLED="1"
> -       export CFLAGS=""
> -       export LDFLAGS=""
> -       export CGO_CFLAGS="${BUILDSDK_CFLAGS} --sysroot=${STAGING_DIR_TARGET}"
>         export GO_GCFLAGS=""
> -       export CGO_LDFLAGS="${BUILDSDK_LDFLAGS} --sysroot=${STAGING_DIR_TARGET}"
>         export GO111MODULE=off
>
>         cd ${S}
> --
> 2.36.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#7356): 
> https://lists.yoctoproject.org/g/meta-virtualization/message/7356
> Mute This Topic: https://lists.yoctoproject.org/mt/91662218/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: 
> https://lists.yoctoproject.org/g/meta-virtualization/unsub 
> [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

  reply	other threads:[~2022-06-10 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  4:20 [meta-virtualization][master][kirkstone][PATCH 1/3] docker-distribution: fix the inehrit and systemd settings Chen Qi
2022-06-10  4:20 ` [meta-virtualization][master][kirkstone][PATCH 2/3] docker-distribution: fix build error on new hosts Chen Qi
2022-06-10 13:00   ` Bruce Ashfield
2022-06-10 13:58     ` Chen, Qi [this message]
2022-06-10 14:03       ` Bruce Ashfield
2022-06-10  4:20 ` [meta-virtualization][master][kirkstone][PATCH 3/3] docker-distribution: upgrade to 2.8.1 Chen Qi

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=CO6PR11MB56025C31C487BD7ECF4EA2C1EDA69@CO6PR11MB5602.namprd11.prod.outlook.com \
    --to=qi.chen@windriver.com \
    --cc=bruce.ashfield@gmail.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 NNTP newsgroup(s).