From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3733] New: dropbear: make zlib optional
Date: Mon, 16 May 2011 19:37:40 +0000 (UTC) [thread overview]
Message-ID: <bug-3733-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3733
Summary: dropbear: make zlib optional
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: patch
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: alex at digriz.org.uk
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I noticed for my buildroot environment the only componment that was pulling in
zlib was dropbear. The patch included drops the zlib dependency when compiling
with DROPBEAR_SMALL, pruning ~70kB for a LZO compressed root which is handy for
me with my 4MB NAND.
No idea if the patch is 'correct' by your standards but it gets my usual
stamps, 'seal of approval' and 'works for me'...
Cheers
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-05-16 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:37 bugzilla at busybox.net [this message]
2011-05-16 19:39 ` [Buildroot] [Bug 3733] dropbear: make zlib optional bugzilla at busybox.net
2011-05-16 20:43 ` bugzilla at busybox.net
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=bug-3733-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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