From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: devshell not working with screen remote shell
Date: Mon, 20 Apr 2009 09:40:17 +0200 [thread overview]
Message-ID: <49EC26E1.8020909@gmail.com> (raw)
In-Reply-To: <6978a1740904192319w5ed4ec4bs4c854ecdc540aaa4@mail.gmail.com>
s hakkesteegt ha scritto:
> You might want to add this to your local.conf
>
> TERMCMD = "${SCREEN_TERMCMD}"
> TERMCMDRUN = "${SCREEN_TERMCMDRUN}"
>
> devshell will open in a new screen session, witch you can attach to
> manually.
>
Siebren,
thank you for answering.
I am using a remote ssh connection to the OE development server and I
use screen package inside it.
I tried adding your lines and now the build stops here
NOTE: package bluez-utils-3.36-r5: task do_devshell: started
but nothing happens.
Are you using this with the same conditions (remote ssh + screen) or
locally?
/marco
next prev parent reply other threads:[~2009-04-20 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 18:35 devshell not working with screen remote shell Marco Cavallini
2009-04-20 6:19 ` s hakkesteegt
2009-04-20 7:40 ` Marco Cavallini [this message]
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=49EC26E1.8020909@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.