All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: ltp@lists.linux.it
Subject: [LTP] Building LTP despite failures
Date: Tue, 17 Jan 2017 11:24:59 -0800	[thread overview]
Message-ID: <ffddd703-ed2a-2d90-bdaa-829aa692646c@synopsys.com> (raw)

Hi,

We use LTP regularly to check the health of ARC Linux. One the pain points have
been out of tree patches to LTP to avoid building lot of stuff which are either
not provided by C library (say uClibc) or not configured in uClibc etc. It seems
we can't use make -k to keep ignoring errors and continue with whatever can be
built. I'm not too bright with makefiles so perhaps there is something I'm missing.
Do people have ideas or have solved this already with LTP.

Thx,
-Vineet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20170117/5cf93895/attachment.html>

             reply	other threads:[~2017-01-17 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 19:24 Vineet Gupta [this message]
2017-01-17 19:25 [LTP] Building LTP despite failures Vineet Gupta
2017-01-18 10:37 ` Cyril Hrubis
2017-01-18 17:13   ` Vineet Gupta
2017-01-19 13:47     ` Cyril Hrubis

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=ffddd703-ed2a-2d90-bdaa-829aa692646c@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=ltp@lists.linux.it \
    /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.