From: Markus Volk <f_l_k@t-online.de>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Problems getting build appliance to work
Date: Sun, 16 Oct 2016 10:25:12 +0200 [thread overview]
Message-ID: <f390bb91-935c-77d0-55a3-c144c74a647f@t-online.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
Hi,
i have created an image for genericx86 from the krogoth branch and would
like to integrate a build appliance. I used build-appliance-image.bb as
a template.
However, there is still something missing. When I run bitbake, i’m
getting a loop.
After aborting by [strg + c] I get this output and also have the same
behavior when cloning poky and my meta layer in the running image,
instead of building it into
builder ~ $ cd poky/git/
builder ~/poky/git $ . ./oe-init-build-env
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
builder ~/poky/git/build $ bitbake -e
^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python3.5/multiprocessing/popen_fork.py", line 29, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
WARNING: Timeout while attempting to communicate with bitbake server
WARNING: Timeout while attempting to communicate with bitbake server
WARNING: Timeout while attempting to communicate with bitbake server
WARNING: Timeout while attempting to communicate with bitbake server
ERROR: Gave up; Too many tries: timeout while attempting to communicate
with bitbake server
ERROR: Could not connect to server None:
I have no idea what i am missing here.
Who can give me a tip?
[-- Attachment #2: Type: text/html, Size: 4640 bytes --]
reply other threads:[~2016-10-16 8:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f390bb91-935c-77d0-55a3-c144c74a647f@t-online.de \
--to=f_l_k@t-online.de \
--cc=yocto@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 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.