Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "JD Schroeder" <sweng5080@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] distcc: Fix groupname gid change warning
Date: Wed, 27 Sep 2023 06:07:10 -0700	[thread overview]
Message-ID: <15368.1695820030017039130@lists.openembedded.org> (raw)
In-Reply-To: <D7F71619-5603-498D-AF15-8AB767ED150F@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

On Tue, Sep 12, 2023 at 06:03 AM, Ross Burton wrote:

> 
> On 1 Sep 2023, at 11:03, Alexandre Belloni via lists.openembedded.org
> <alexandre.belloni=bootlin.com@lists.openembedded.org> wrote:
> 
>> 
>> Hello,
>> 
>> This fails on the autobuilders:
>> 
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/3449/steps/12/logs/stdio
>> 
>> 
>> ERROR: Nothing RPROVIDES 'distcc' (but
>> /home/pokybuild/yocto-worker/reproducible/build/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb,
>> /home/pokybuild/yocto-worker/reproducible/build/meta/recipes-devtools/devel-config/distcc-config.bb
>> RDEPENDS on or otherwise requires it)
>> distcc was skipped: Recipe distcc, package distcc-server: system groupname
>> "nogroup" does not have a static ID defined. Add nogroup to one of these
>> files:
>> /home/pokybuild/yocto-worker/reproducible/build/build-st/meta-selftest/files/static-group
>> 
> 
> The same problem would hit the ppp-dialin but that recipe doesn’t get
> built in the AB in an environment that has static IPs.
> 
> Ross

I'm seeing the the warnings being generated in a multi-config Yocto build environment. Is there another way to address and fix the warnings I am having with the distcc and ppp-dialin recipes (possibly during parsing) even if they aren't being built in the AB with static IPs?

[-- Attachment #2: Type: text/html, Size: 1524 bytes --]

  reply	other threads:[~2023-09-27 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 14:23 [PATCH 1/2] distcc: Fix groupname gid change warning JD Schroeder
2023-08-31 14:23 ` [PATCH 2/2] ppp-dialin: " JD Schroeder
2023-09-01 10:03 ` [OE-core] [PATCH 1/2] distcc: " Alexandre Belloni
2023-09-12 11:03   ` Ross Burton
2023-09-27 13:07     ` JD Schroeder [this message]
2023-09-27 14:01       ` Richard Purdie
2023-10-26 13:50         ` JD Schroeder

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=15368.1695820030017039130@lists.openembedded.org \
    --to=sweng5080@gmail.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