linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: [PATCH] Makefile.am: add mkdir testsuite and standaline build target
Date: Wed, 09 Oct 2013 17:39:24 -0700	[thread overview]
Message-ID: <5255F73C.6050908@linux.intel.com> (raw)
In-Reply-To: <CAKi4VALxoEXMu5DQBZbX9ckGCtSX6-EF7ehnLtLPxF9PumUE+g@mail.gmail.com>

On 10/09/2013 04:30 PM, Lucas De Marchi wrote:
> Hi Saul,
>
> On Wed, Oct 9, 2013 at 7:53 PM, Saul Wold <sgw@linux.intel.com> wrote:
>> If we are not building in the existing source tree, the testsuite
>> directory will not exist so the cp of the stamp-rootfs would fail.
>>
>> Also added buildtest-TESTS so they could be build in the cross env,
>> without running the tests.
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>>   Makefile.am | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/Makefile.am b/Makefile.am
>> index c165868..018e6ed 100644
>> --- a/Makefile.am
>> +++ b/Makefile.am
>> @@ -131,7 +131,7 @@ endif
>>
>>   ROOTFS = testsuite/rootfs
>>   ROOTFS_PRISTINE = $(top_srcdir)/testsuite/rootfs-pristine
>> -CREATE_ROOTFS = $(AM_V_GEN) ( $(RM) -rf $(ROOTFS) && \
>> +CREATE_ROOTFS = $(AM_V_GEN) ( $(RM) -rf $(ROOTFS) && mkdir -p $(dir $(ROOTFS)) && \
>
> I think it's something else that's causing a failure for you.  The
> following works for me:
>
> $ ./autogen.sh
> $ cd /tmp/build
> $ $OLDPWD/configure --sysconfdir=/etc --with-zlib && make -j10 check
>
> You really need the --sysconfdir=/etc and --with-zlib otherwise some
> tests will fail.  These are the flags we pass to distcheck, that also
> builds out of tree (but in an inner directory)
>
Since I am not running check on the build machine, I am running check on 
the target, I create an installable package that includes the rootfs and 
tests, to this I run make rootfs on the build machine, can you veify 
that that works in a clean build directory?

Since the make check above will create the testsuite directory and build 
all the tests before rootfs target is called, in my case that does not 
happen.


>>                                  cp -r $(ROOTFS_PRISTINE) $(ROOTFS) && \
>>                                  touch testsuite/stamp-rootfs && \
>>                                  find $(ROOTFS) -type d -exec chmod +w {} \; )
>> @@ -217,6 +217,9 @@ DISTCHECK_CONFIGURE_FLAGS=--enable-gtk-doc --sysconfdir=/etc --with-zlib
>>
>>   distclean-local: $(DISTCLEAN_LOCAL_HOOKS)
>>
>> +buildtest-TESTS:
>> +       $(MAKE) $(AM_MAKEFLAGS) $(check_LTLIBRARIES) $(check_PROGRAMS)
>> +
>
> Makes sense. Splitting the patch would be good.
>

Do you still want this split based on the above observation?

Sau!
> Thanks
> Lucas De Marchi
>

  reply	other threads:[~2013-10-10  0:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 22:53 [PATCH] Makefile.am: add mkdir testsuite and standaline build target Saul Wold
2013-10-09 23:30 ` Lucas De Marchi
2013-10-10  0:39   ` Saul Wold [this message]
2013-10-10  0:55     ` Lucas De Marchi
2013-10-10  1:14       ` Saul Wold
2013-10-10  4:15         ` Lucas De Marchi

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=5255F73C.6050908@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).