From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 1/1] mosh: new package
Date: Mon, 27 Jul 2015 01:20:39 +0300 [thread overview]
Message-ID: <20150726222039.GL17029@tarshish> (raw)
In-Reply-To: <1437928447-26907-1-git-send-email-christian@paral.in>
Hi Christian,
On Sun, Jul 26, 2015 at 09:34:07AM -0700, Christian Stewart wrote:
> diff --git a/package/mosh/Config.in b/package/mosh/Config.in
> new file mode 100644
> index 0000000..9841b2e
> --- /dev/null
> +++ b/package/mosh/Config.in
> @@ -0,0 +1,19 @@
> +comment "mosh needs a toolchain w/ threads"
> + depends on !BR2_TOOLCHAIN_HAS_THREADS
The dependencies comment should depend on supported arches. Since this patch
has already been applied, I'll send a follow-up.
> +config BR2_PACKAGE_MOSH
> + bool "mosh"
> + depends on BR2_arm || BR2_i386 || BR2_mipsel || BR2_x86_64 # protobuf
> + depends on BR2_TOOLCHAIN_HAS_THREADS #protobuf
> + depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" # protobuf
> + select BR2_PACKAGE_PROTOBUF
> + select BR2_PACKAGE_NCURSES
> + select BR2_PACKAGE_OPENSSL
> + select BR2_PACKAGE_OPENSSH if !BR2_PACKAGE_DROPBEAR_CLIENT
> + select BR2_PACKAGE_ZLIB
> + help
> + Remote terminal application that supports intermittent connectivity,
> + allows roaming, and provides speculative local echo and line editing
> + of user keystrokes.
> +
> + https://mosh.mit.edu
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2015-07-26 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 16:34 [Buildroot] [PATCH v8 1/1] mosh: new package Christian Stewart
2015-07-26 17:01 ` Yann E. MORIN
2015-07-26 17:35 ` Thomas Petazzoni
2015-07-26 18:02 ` Christian Stewart
2015-07-26 19:41 ` Thomas Petazzoni
2015-07-27 21:38 ` Christian Stewart
2015-07-26 22:20 ` Baruch Siach [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=20150726222039.GL17029@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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