From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
Cc: linux-mtd@lists.infradead.org, Florian Fainelli <ffainelli@freebox.fr>
Subject: Re: [PATCHv2] tests: introduce new target tests in Makefile
Date: Thu, 07 Apr 2011 13:44:39 +0300 [thread overview]
Message-ID: <1302173079.2407.30.camel@localhost> (raw)
In-Reply-To: <2016ea1c9296efd368a37e4f869bd8a51f20c537.1302015688.git.ext-andriy.shevchenko@nokia.com>
On Tue, 2011-04-05 at 18:03 +0300, Andy Shevchenko wrote:
> This patch appends Makefile to the tests subdirectory and introduces tests
> target in the root Makefile.
>
> Additionally the clean target removes temporary stuff under tests subdirectory
> as well.
>
> Signed-off-by: Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
> ---
> Makefile | 7 ++++++-
> tests/Makefile | 8 ++++++++
> 2 files changed, 14 insertions(+), 1 deletions(-)
> create mode 100644 tests/Makefile
Breaks compilation for me:
[dedekind@eru mtd-utils (master)]$ make
d=lib_all; \
t=`echo $d | sed s:.*_::` d=`echo $d | sed s:_.*::`; \
make BUILDDIR=/home/dedekind/git/mtd-utils/$d -C $d $t
make[1]: Entering directory `/home/dedekind/git/mtd-utils/lib'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/dedekind/git/mtd-utils/lib'
ar crv /home/dedekind/git/mtd-utils/lib/libmtd.a subdirs_lib_all
ar: subdirs_lib_all: No such file or directory
make: *** [/home/dedekind/git/mtd-utils/lib/libmtd.a] Error 1
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-07 10:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 11:33 [PATCHv1 1/3] tests: make jittertest buildable Andy Shevchenko
2011-04-05 11:33 ` [PATCHv1 2/3] tests: build tests by default Andy Shevchenko
2011-04-05 12:44 ` Josh Boyer
2011-04-05 12:45 ` Artem Bityutskiy
2011-04-05 12:57 ` Florian Fainelli
2011-04-05 15:03 ` [PATCHv2] tests: introduce new target tests in Makefile Andy Shevchenko
2011-04-06 8:53 ` Artem Bityutskiy
2011-04-06 9:04 ` Florian Fainelli
2011-04-07 10:44 ` Artem Bityutskiy [this message]
2011-04-07 13:10 ` Andy Shevchenko
2011-04-07 13:10 ` Artem Bityutskiy
2011-04-07 13:27 ` Andy Shevchenko
2011-04-07 13:44 ` Artem Bityutskiy
2011-04-05 11:33 ` [PATCHv1 3/3] tests: fix compiler warnings Andy Shevchenko
2011-04-05 12:52 ` Artem Bityutskiy
2011-04-05 13:08 ` Andy Shevchenko
2011-04-05 13:55 ` [PATCHv1 1/5] tests: checkfs: " Andy Shevchenko
2011-04-05 13:55 ` [PATCHv1 2/5] tests: checkfs: fix linker warnings Andy Shevchenko
2011-04-05 14:15 ` Artem Bityutskiy
2011-04-05 13:55 ` [PATCHv1 3/5] tests: fs-tests: check return value of functions Andy Shevchenko
2011-04-05 14:17 ` Artem Bityutskiy
2011-04-05 13:55 ` [PATCHv1 4/5] tests: jittertest: fix set of compiler warnings Andy Shevchenko
2011-04-05 14:20 ` Artem Bityutskiy
2011-04-05 14:32 ` [PATCHv2] " Andy Shevchenko
2011-04-05 14:39 ` Artem Bityutskiy
2011-04-05 13:55 ` [PATCHv1 5/5] tests: ubi-tests: seed_random_generator() was used w/o prototype Andy Shevchenko
2011-04-05 14:22 ` Artem Bityutskiy
2011-04-05 14:08 ` [PATCHv1 1/5] tests: checkfs: fix compiler warnings Artem Bityutskiy
2011-04-05 12:51 ` [PATCHv1 1/3] tests: make jittertest buildable Artem Bityutskiy
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=1302173079.2407.30.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=ext-andriy.shevchenko@nokia.com \
--cc=ffainelli@freebox.fr \
--cc=linux-mtd@lists.infradead.org \
/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