All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: 'Kalle Valo' <kvalo@codeaurora.org>, riku.voipio@linaro.org
Cc: linux-kbuild@vger.kernel.org, mmarek@suse.cz,
	ben@decadent.org.uk, Doug Smythies <dsmythies@telus.net>
Subject: RE: [PATCH v2] builddeb: remove debian/files before build
Date: Tue, 15 Sep 2015 12:11:31 -0700	[thread overview]
Message-ID: <001f01d0efea$56135e40$023a1ac0$@net> (raw)
In-Reply-To: <8737yfy24g.fsf@kamboji.qca.qualcomm.com>

On 2015.09.15 11:22 Kalle Valo wrote:
> <riku.voipio@linaro.org> writes:
>> From: Riku Voipio <riku.voipio@linaro.org>
>>
>> As debian/files keeps accumulating entries, the changes file
>> will end up growing indefinelty. Remove the file in clean
>> rule and before build starts.
>>
>> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
>> Reported-by: Doug Smythies <dsmythies@telus.net>

> Thanks, I had the same problem and this fixed it.
> Tested-by: Kalle Valo <kvalo@codeaurora.org>

I tested also. Thanks.

For an incremental compile, where only one source file
has changed, the time went from 7 minutes and 47 seconds
to 4 minutes and 33 seconds on my test server.
And the spew of warnings and such are gone.

For reference a clean compile typically takes about
23 minutes.

The overhead for making the .changes file is now on the
order of 2 to 4 seconds.

Obviously, results will vary widely for others, depending
on their hardware.



  reply	other threads:[~2015-09-15 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 18:11 [PATCH v2] builddeb: remove debian/files before build riku.voipio
2015-09-15 18:21 ` Kalle Valo
2015-09-15 19:11   ` Doug Smythies [this message]
2015-09-16  6:55     ` Riku Voipio
2015-09-21 18:09 ` Ben Hutchings
2015-09-22 11:25   ` Kalle Valo
2015-10-05  1:03     ` Doug Smythies
2015-10-05 12:39       ` Riku Voipio
2015-10-05 20:49         ` Andrew Morton
2015-10-06  7:05           ` [PATCH v3] " riku.voipio

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='001f01d0efea$56135e40$023a1ac0$@net' \
    --to=dsmythies@telus.net \
    --cc=ben@decadent.org.uk \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=riku.voipio@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.