From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] decreasing size of compile log
Date: Sun, 27 Jan 2013 21:42:06 +0100 [thread overview]
Message-ID: <87a9rubboh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CALo-6+jBObEiK5reN1qno0bD-ufDK3jX2drKbcwzKLXt=A9reQ@mail.gmail.com> (Charles Krinke's message of "Sun, 27 Jan 2013 12:31:55 -0800")
>>>>> "Charles" == Charles Krinke <charles.krinke@gmail.com> writes:
Charles> Gentlemen:
Charles> I have a nearly finished AM3517 project with buildroot. Thank you all
Charles> for getting me to this point.
Charles> I have an issue where the compile log runs 50000 lines. That
Charles> is, "make clean && make" produces output from all the packages
Charles> being compiled.
Charles> Is there a way to add a string to selected buildroot/package
Charles> directories to tell selected packages to either not print
Charles> their compiled output, send it do /dev/null or minimize the
Charles> printed output during compile so as to focus on the one or two
Charles> packages where there are issues to be solved?
You can compile with make -s (silent) option to make buildroot less
verbose (but it is still quite verbose).
Is the amount of output any real problem, or is it just cosmetical?
Normally if there's any build problems you only really want to look at
the last few lines (which is also why the autobuilder web page provides
a link to the last ~100 lines).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-27 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 20:31 [Buildroot] decreasing size of compile log Charles Krinke
2013-01-27 20:42 ` Peter Korsgaard [this message]
2013-01-27 21:49 ` Charles Krinke
2013-01-27 22:37 ` Peter Korsgaard
2013-01-28 2:15 ` Charles Krinke
2013-01-28 7:47 ` 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=87a9rubboh.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