Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1351] host-libxslt-1.1.24 fails to build
Date: Sun, 21 Mar 2010 08:51:19 +0100	[thread overview]
Message-ID: <20100321085119.3d9104eb@surf> (raw)
In-Reply-To: <4BA59B5A.6090701@iwtech.com.au>

Hello,

On Sun, 21 Mar 2010 15:06:50 +1100
Paul Jones <paul.jones@iwtech.com.au> wrote:

> How do I get a build log?
> make > buildlog.txt ?

I usually do something like:

 make 2>&1 | tee build.log

The problem with "make > buildlog.txt" is that error messages will not
be sent to your log file.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-03-21  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  8:49 [Buildroot] [Bug 1351] New: host-libxslt-1.1.24 fails to build bugzilla at busybox.net
2010-03-18  9:02 ` [Buildroot] [Bug 1351] " bugzilla at busybox.net
2010-03-21  4:06   ` Paul Jones
2010-03-21  7:51     ` Thomas Petazzoni [this message]
2010-04-09 14:54 ` bugzilla at busybox.net
2010-06-25  9:38 ` bugzilla at busybox.net

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=20100321085119.3d9104eb@surf \
    --to=thomas.petazzoni@free-electrons.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