[Bug other/29700] check requires autogen

[gin at mo dot msk dot ru]

--- Comment #6 from gin at mo dot msk dot ru  2006-11-06 17:24 ---
Subject: Re:  check requires autogen

`make' performing all tests is not enough to test successfully.  The
test failures normally result in make error, ignored by `-k' or not.
One looks for such error messages in `make' output.  Having to sieve
out other sorts of errors, those caused by missing `autogen', at least
complicates use of tests and automating it in particular.  This is why
considering `-k' workaround unacceptable.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700

[Bug other/29700] check requires autogen

[ebotcazou at gcc dot gnu dot org]

--- Comment #7 from ebotcazou at gcc dot gnu dot org  2006-11-06 17:33 
---
 `make' performing all tests is not enough to test successfully.  The
 test failures normally result in make error, ignored by `-k' or not.

The GCC testsuite is DejaGNU-based so it is to be invoked with make -k check.

 One looks for such error messages in `make' output.  Having to sieve
 out other sorts of errors, those caused by missing `autogen', at least
 complicates use of tests and automating it in particular.  This is why
 considering `-k' workaround unacceptable.

This is not a workaround.  See http://gcc.gnu.org/install/test.html.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700

[Bug other/29700] check requires autogen

[ebotcazou at gcc dot gnu dot org]

--- Comment #1 from ebotcazou at gcc dot gnu dot org  2006-11-03 19:32 
---
 That this package is required to run tests is not even said in
 INSTALL/test.html.  Neither http://gcc.gnu.org/install/test.html
 says so.  If it indeed has to be required, this is documentation bug.

It is not, the documentation says:

Finally, you can run the testsuite (which may take a long time):

  cd objdir; make -k check


-- 

ebotcazou at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||ebotcazou at gcc dot gnu dot
   ||org
 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700

[Bug other/29700] check requires autogen

[gin at mo dot msk dot ru]

--- Comment #2 from gin at mo dot msk dot ru  2006-11-03 19:43 ---
Subject: Re:  check requires autogen

Certainly ran `make check' in top level build directory, and indicated
that by including parts of `make -w' output, printout of directories
entered and left by `make'.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700

[Bug other/29700] check requires autogen

[ebotcazou at gcc dot gnu dot org]

--- Comment #3 from ebotcazou at gcc dot gnu dot org  2006-11-03 19:52 
---
 Certainly ran `make check' in top level build directory,

Your mistake.  Only 'make -k check' is supported.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700

[Bug other/29700] check requires autogen

[gin at mo dot msk dot ru]

--- Comment #4 from gin at mo dot msk dot ru  2006-11-03 20:03 ---
Subject: Re:  check requires autogen

Sorry for not indicating that.  Always specified `-k' in all `make'
runs.  They yield the results as described.

The gist is that currently the only way to obtain actual test script,
`check.sh', is running `autogen'.  Being unable to make tests in some
subdirectories for that reason certainly may be worked around with
`-k', and that is not a fix.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700

[Bug other/29700] check requires autogen

[ebotcazou at gcc dot gnu dot org]

--- Comment #5 from ebotcazou at gcc dot gnu dot org  2006-11-03 23:36 
---
 Sorry for not indicating that.  Always specified `-k' in all `make'
 runs.  They yield the results as described.

'make check' and 'make -k check' are certainly not equivalent.  The former
will stop if you don't have autogen, the latter will not.  So autogen is
not required to run 'make -k check'.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29700