From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: devshell not working with screen remote shell
Date: Sun, 19 Apr 2009 20:35:46 +0200 [thread overview]
Message-ID: <49EB6F02.1030402@gmail.com> (raw)
devshell is not working when you run bitbake in a screen remote ssh shell
(also potest here http://bugs.openembedded.net/show_bug.cgi?id=5084)
$ bitbake -cdevshell bluez-utils
NOTE: Handling BitBake files: - (6658/6658) [100 %]
NOTE: Parsing finished. 6398 cached, 0 parsed, 260 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200904192010: started
OE Build Configuration:
BB_VERSION = "1.8.13"
METADATA_BRANCH = "stable/2009"
METADATA_REVISION = "6ea387ca312c4686746c387b56735f7b96f599b3"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "kaeilos"
DISTRO_VERSION = "2008.1-test-20090419"
NOTE: oestats: build 140918
...snip...
NOTE: package bluez-utils-3.36-r5: task do_patch: completed
NOTE: Running task 32 of 32 (ID: 4,
/home/koan/devel/openembedded/recipes/bluez/bluez-utils_3.36.bb,
do_devshell)
NOTE: package bluez-utils-3.36-r5: task do_devshell: started
ERROR: function do_devshell failed
ERROR: log data follows
(/home/koan/devel/build/kaeilos/tmp/work/i586-kaeilos-linux/bluez-utils-3.36-r5/temp/log.do_devshell.5388)
| cannot open display:
| Run 'gnome-terminal --help' to see a full list of available command line
options.
I already tried to solve this time ago using different option in bitbake
code
(trying to activate xterm instead of the default x terminal) and trying
to set
DISPLAY and xauth in several ways without success.
/marco
next reply other threads:[~2009-04-19 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 18:35 Marco Cavallini [this message]
2009-04-20 6:19 ` devshell not working with screen remote shell s hakkesteegt
2009-04-20 7:40 ` Marco Cavallini
2009-04-20 8:37 ` s hakkesteegt
2009-04-20 7:49 ` Marco Cavallini
2009-04-27 14:18 ` Sledz, Steffen
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=49EB6F02.1030402@gmail.com \
--to=koansoftware@gmail.com \
--cc=openembedded-devel@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 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.