From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] core/instrumentation: shave minutes off the build time
Date: Sun, 18 Mar 2018 17:33:45 +0100 [thread overview]
Message-ID: <87efkhfimu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180318161530.GA2478@scaer> (Yann E. MORIN's message of "Sun, 18 Mar 2018 17:15:30 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> - It doesn't work for packages using rsync to install,
>> E.G. skeleton-init-common as rsync also sets the mtime to match the
>> source files
> We could maybe tell rsycn not to do that, then?
Yes, possibly.
>> - It breaks for <pkg>-reinstall
> Well, we can't guarantee anything except with a clean build from scratch
> anyway.
True. We could potentionally do a touch on the stamp file before running
find, but it is somewhat icky.
>> I don't think either of those are really big issues compared to the huge
>> slowdown, but it is worth noticing.
> Well, the -reinstall was already not working correctly, because the list
> pf files before/after would be alsmost the same, and the md5-diff would
> miss all the laready-installed files for the package.
> The rsync issue is new, but we can "fix" it in a later patch, then, for
> those packages like the skeletons, by using the --no-times option for
> example.
Yes. I guess we cannot use --no-times unconditionally in SYSTEM_RSYNC,
as the mtime shouldn't be touched for source files so OVERRIDE_SRCDIR
doesn't rebuild too much.
> However, if a third-party package internally uses rsync as its install
> method, we're screwed. But who would be insane enough to do that? ;-]
And even so, the breakage is not so bad.
> Alternatively, we could use ctime instead of mtime, maybe? Or check
> both?
ctime would presumably miss modifications to existing files, so that is
no good.
>> > +define step_pkg_size_inner
>> > + cd $(2); \
>> > + find . \( -type f -o -type L \) \
>> > + -newer $($(PKG)_DIR)/.stamp_built \
>> > + -exec printf '$(1),%s\n' {} + \
>> > + >> $(BUILD_DIR)/packages-file-list$(3).txt
>>
>> What find version are you using? My fileutils find (and the busybox
>> applet) use 'l' for symlinks, so I've changed it to that.
> Doh, the s/L/l/ is still uncomitted here. Dang...
;)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-18 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 20:35 [Buildroot] [PATCH 0/2] core/instrumentation: optimisations Yann E. MORIN
2018-03-15 20:35 ` [Buildroot] [PATCH 1/2] core/intrumetnation: don't spawn to get seconds-since-EPOCH Yann E. MORIN
2018-03-17 11:54 ` Cam Hutchison
2018-03-18 16:16 ` Yann E. MORIN
2018-03-19 16:15 ` Trent Piepho
2018-03-15 20:35 ` [Buildroot] [PATCH 2/2] core/instrumentation: shave minutes off the build time Yann E. MORIN
2018-03-18 14:14 ` Peter Korsgaard
2018-03-18 16:15 ` Yann E. MORIN
2018-03-18 16:33 ` Peter Korsgaard [this message]
2018-03-22 16:41 ` Thomas De Schampheleire
2018-03-22 16:50 ` Thomas Petazzoni
2018-03-22 17:11 ` Thomas De Schampheleire
2018-03-22 17:25 ` Trent Piepho
2018-03-22 22:39 ` Peter Korsgaard
2018-03-23 22:39 ` Arnout Vandecappelle
2018-03-23 23:03 ` Thomas Petazzoni
2018-03-19 16:30 ` Trent Piepho
2018-03-19 16:50 ` Thomas Petazzoni
2018-03-19 20:04 ` Peter Korsgaard
2018-03-20 21:47 ` Trent Piepho
2018-03-19 16:53 ` 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=87efkhfimu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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