From: Randy MacLeod <randy.macleod@windriver.com>
To: bhstalel@gmail.com, poky@lists.yoctoproject.org
Subject: Re: [poky] Failed to spawn fakeroot worker: Broken Pipe Issue
Date: Fri, 3 May 2024 21:39:05 -0400 [thread overview]
Message-ID: <34f7765a-22da-4b3a-95a0-952f7c47186b@windriver.com> (raw)
In-Reply-To: <OGzg.1713784502488483155.cwqW@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On 2024-04-22 7:15 a.m., BELHADJ SALEM Talel via lists.yoctoproject.org
wrote:
> Hello All,
>
> I am really confused with the following error:
>
> *ERROR: Failed to spawn fakeroot worker to run
> /home/talel.hajsalem/Documents/FinalGit/easyocto/test_output/layers/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.4.bb:do_install:
> [Errno 32] Broken pipe*
> *WARNING:
> /home/talel.hajsalem/.../layers/poky/bitbake/lib/bb/runqueue.py:2229:
> ResourceWarning: unclosed file <_io.BufferedWriter name=31>*
> * return True*
> *WARNING:
> /home/talel.hajsalem/.../layers/poky/bitbake/lib/bb/runqueue.py:2229:
> ResourceWarning: unclosed file <_io.BufferedReader name=32>*
> * return True*
>
> Everything is owned by my regular user, and I have nothing changed in
> my setup, suddenly this error showed up.
>
> I even tried to clean all sstate and remove the entire build and try
> from zero. I even restarted the system.
>
> Any clue ?
Hi,
Hopefully you've solved this by now.
What command did you type that produced this error?
Did things work well before? What changed recently?
What branch are you using and can you reproduce the problem with just Poky?
What can you tell us about your build system and what else is running on
it? It seem like you might have exhausted memory.
../Randy
[-- Attachment #2: Type: text/html, Size: 2194 bytes --]
prev parent reply other threads:[~2024-05-04 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 11:15 Failed to spawn fakeroot worker: Broken Pipe Issue BELHADJ SALEM Talel
2024-05-04 1:39 ` Randy MacLeod [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=34f7765a-22da-4b3a-95a0-952f7c47186b@windriver.com \
--to=randy.macleod@windriver.com \
--cc=bhstalel@gmail.com \
--cc=poky@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).