[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to run tests for sed?

From: kk
Subject: Re: How to run tests for sed?
Date: Tue, 14 Mar 2017 10:09:00 +0800

Thanks for the explanation in detail.

I just want to let the testcases run on the target when I did the cross compiling. 

My problem was that I don't know copy what files on the target, and how to run on the target, so I need to read the

On host, just "make check".

On Mon, Mar 13, 2017 at 1:33 PM, Assaf Gordon <address@hidden> wrote:

> On Mar 12, 2017, at 23:35, kk <address@hidden> wrote:
> Thanks first, I have some doubt about the file.

I would recommend avoiding dealing with '' directly, unless
you are interested (or troubleshooting) the nitty-gritty details
of GNU automake. It is automake that reads <sed>/testsuite/
and generates (lots of) targets that eventually help 'make check' "just work".

In ./testsuite/  every item listed to the TESTS variable will
become a test when running 'make check' - regardless
of whether it is a recursive build system or not.

> I see the target "check", it's rule was : $(MAKE) $(AM_MAKEFLAGS) check-recursive, but the check-recursive was a member of RECURSIVE_TARGETS, how it find and build the tests?

This is part of automake's complicated system.
I do not claim to be an automake expert, but I can offer some pointers:

If you run "make --just-print check-recursive" you'll see:

    $ make --just-print check-recursive
    target=`echo check-recursive | sed s/-recursive//`;

This command is part of a target definition of "$(am__recursive_targets)",
which expands to multiple targets (including 'check-recursive').

This variable is created with:
   am__recursive_targets = \

And 'RECURSIVE_TARGETS' iteslf contains 'check-recursive':

     RECURSIVE_TARGETS = all-recursive check-recursive [...]

Again, I wouldn't recommend going down that path unless you are debugging automake

Running 'make check' should build programs required for testing (there are only
two small C programs needed for the tests), and then executes the actual tests
(which are shell scripts and do not require any building).

If there is a problem in the tests (e.g. a test that does not execute correctly),
please report it - it's a bug.

Two known bugs regarding tests are running tests under windows, and
enabling the old regex extended tests - currently there is no fix for this issues (patches welcomed).

If you'd like to add tests - please add them to ./testsuite/,
not to directly.

Hope this helps,

  - assaf

reply via email to

[Prev in Thread] Current Thread [Next in Thread]