From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] SVN process started at make
Date: Tue, 03 Sep 2013 16:50:27 +0200 [thread overview]
Message-ID: <87sixm558s.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <15AE5A936F5E3A42A9144E66875A0A8934DB3B@server1-derijp.CLB-Benelux.lokaal> (Ruud Commandeur's message of "Tue, 3 Sep 2013 16:37:44 +0200")
>>>>> "Ruud" == Ruud Commandeur <RCommandeur@clb.nl> writes:
Ruud> Hi Everyone,
Ruud> Since today, all my 'make' commands in the buildroot dir take a very
Ruud> long time before they actually start doing something. It appears to be
Ruud> that on each make command, an svn process is started, that takes 5-10%
Ruud> CPU time for a couple of minutes. Once this process stops, the 'normal'
Ruud> make actions start.
Ruud> My sources have been under svn control for a long time by using
Ruud> SmartSVN, but since today I installed the commandline tool of
Ruud> subversion. This must have triggered this behaviour, but can anyone
Ruud> explain to me how I can prevent this? Is this someting in the
Ruud> Makefile(s)?
Odd. Would it be because of ./support/scripts/setlocalversion?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-09-03 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 14:37 [Buildroot] SVN process started at make Ruud Commandeur
2013-09-03 14:50 ` Peter Korsgaard [this message]
2013-09-03 16:28 ` Arnout Vandecappelle
2013-09-04 7:55 ` Ruud Commandeur
2013-09-04 8:07 ` Thomas Petazzoni
2013-09-04 8:57 ` Ruud Commandeur
2013-09-04 9:15 ` Peter Korsgaard
2013-09-04 10:02 ` Peter Korsgaard
2013-09-04 11:49 ` Ruud Commandeur
2013-09-04 11:26 ` Ruud Commandeur
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=87sixm558s.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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