From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Oleg Lyovin via buildroot <buildroot@buildroot.org>
Cc: John Stile <johns@msli.com>,
olegartys@gmail.com, Oleg Lyovin <ovlevin@salutedevices.com>
Subject: Re: [Buildroot] [PATCH 1/1] package: dhcpcd: fix dhcpcd binary not stripped
Date: Wed, 8 Nov 2023 23:26:44 +0100 [thread overview]
Message-ID: <20231108232644.24817d72@windsurf> (raw)
In-Reply-To: <20231107132323.3324587-1-ovlevin@salutedevices.com>
Hello Oleg,
On Tue, 7 Nov 2023 16:23:23 +0300
Oleg Lyovin via buildroot <buildroot@buildroot.org> wrote:
> By default dhcpcd installed with 555 permissions as it is
> configured in its Makefile.inc. Since 'w' bit is missing,
> strip fails and dhcpcd binary installed non-stripped.
Wow, very good finding!
> On ARM GCC 12 glibc configuration strip saves over 1MB of disk space.
Could you clarify in which configuration you found that over 1 MB of
disk space gets saved?
Here, my dhcpcd binary, unstripped looks like this:
-r-xr-xr-x. 1 thomas thomas 327K 8 nov. 23:22 dhcpcd
So, 327 KB. How can 1 MB be saved?
(Note: of course this doesn't remove anything to the relevance of your
patch, but I'm curious how you got that number).
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-08 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 13:23 [Buildroot] [PATCH 1/1] package: dhcpcd: fix dhcpcd binary not stripped Oleg Lyovin via buildroot
2023-11-08 22:26 ` Thomas Petazzoni via buildroot [this message]
2023-11-09 8:05 ` Oleg Lyovin via buildroot
2023-11-11 13:42 ` Peter Korsgaard
2023-11-13 13:00 ` 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=20231108232644.24817d72@windsurf \
--to=buildroot@buildroot.org \
--cc=johns@msli.com \
--cc=olegartys@gmail.com \
--cc=ovlevin@salutedevices.com \
--cc=thomas.petazzoni@bootlin.com \
/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