From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V4 1/2] dropbear: bump to version 2018.76
Date: Sat, 28 Apr 2018 17:49:41 +0200 [thread overview]
Message-ID: <20180428174941.711ad03b@windsurf> (raw)
In-Reply-To: <20180328083827.31540-1-francois.perrad@gadz.org>
Hello,
On Wed, 28 Mar 2018 10:38:26 +0200, Francois Perrad wrote:
> with this new version:
> - "configure --enable-static" should now be used instead of
> "make STATIC=1"
> - any customised options should be put in localoptions.h
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/dropbear/dropbear.hash | 2 +-
> package/dropbear/dropbear.mk | 31 ++++++++++++++-----------------
> 2 files changed, 15 insertions(+), 18 deletions(-)
I've applied to master, after doing some minor changes:
- DROPBEAR_POST_EXTRACT_HOOKS += DROPBEAR_SVR_PASSWORD_AUTH was moved
closer to where DROPBEAR_SVR_PASSWORD_AUTH is defined
- A comment was added on top of DROPBEAR_SVR_PASSWORD_AUTH to explain
why we're doing this.
In addition, after applying/pushing your commit, I had a build failure
with non-SSP toolchains, so I made a separate commit to fix this:
https://git.buildroot.org/buildroot/commit/?id=b0aafef6198ee292c4f426295e92cc9b601c2338
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-28 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 8:38 [Buildroot] [V4 1/2] dropbear: bump to version 2018.76 Francois Perrad
2018-03-28 8:38 ` [Buildroot] [V4 2/2] dropbear: unbundle libtomath & libtomcrypt Francois Perrad
2018-04-28 15:50 ` Thomas Petazzoni
2018-03-28 11:51 ` [Buildroot] [V4 1/2] dropbear: bump to version 2018.76 Thomas Petazzoni
2018-03-28 14:41 ` François Perrad
2018-03-28 14:42 ` Thomas Petazzoni
2018-04-28 15:49 ` Thomas Petazzoni [this message]
2018-08-27 9:37 ` Peter Korsgaard
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=20180428174941.711ad03b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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