public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] out of tree build
Date: Mon, 10 Mar 2014 13:50:58 +0100	[thread overview]
Message-ID: <20140310125058.GA10346@rei> (raw)
In-Reply-To: <531CAEB1.3060905@xenomai.org>

Hi!
> Hi,
> 
> I have tried building LTP january release, and found that the following 
> changes were necessary.

We did not test it for some time (I've looked at the history and it has
been broken for at least two years) sorry.

Now to the patch. Generally it looks good to me, most of the changes are
fixes in paths that should not break anything.

Have you tried in tree build with the changes, was it working fine?

Does the patch apply over the latest git? Ideally you should send a
signed patch against latest git (output from git format-patch).

And it would be a good idea to add out-of-tree build instructions into
the doc/mini-howto-building-ltp-from-git.txt too.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-03-10 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09 18:10 [LTP] out of tree build Gilles Chanteperdrix
2014-03-10 12:50 ` chrubis [this message]
2014-03-22 19:33   ` [LTP] [PATCH] build: fix out-of-tree build Gilles Chanteperdrix
2014-03-26 15:06     ` chrubis

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=20140310125058.GA10346@rei \
    --to=chrubis@suse.cz \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=ltp-list@lists.sourceforge.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