Re: Understanding the tests

[Tim Van Holder]

[Please reply to the bison list, not a specific poster]

> I followed your suggestion and 'make' replied that there was 
> nothing to 
> be done.  The tests still reference v1.28 which is in /usr/local/bin. 
> Is it necessary to INSTALL before doing these tests?  That 
> does not seem 
> right?
> 
> FWIW, I've attached the new logfile.

Ah - I see - it has nothing to do with bison not being built:

PATH: /Users/mpmcl/Projects/Bison
PATH: Flex/bison-1.875/tests
PATH: /usr/bin

You seem to have made the unfortunate mistake of using a ':' in a
directory name.  This is seen as a path separator, so the 'tests'
directory (which has a wrapper script for bison) isn't actually
in PATH.  As a result, the next best bison (the one in /usr/bin)
is used.
Rename the 'Bison:Flex' directory and things should work.

> 
> Tim Van Holder wrote:
> > On Thu, 2003-03-20 at 16:27, Michael McLaughlin wrote:
> > 
> >>Hello,
> >>
> >>Apologies for a newbie question.
> >>
> >>I downloaded GNU Bison 1.875, ran configure and then
> >>
> >>make check > testYACC.txt
> >>
> >>under Mac OS 10.2.4 ("freeBSD").
> >>
> >>Judging by all the "FAILED" statements (log attached), it 
> does not look 
> >>good.  However, I have no clue as to where to begin to try 
> to understand 
> >>all of these tests and their results.
> > 
> > 
> > Actually it seems the checks are using bison from the path 
> (i.e. bison
> > 1.28), so lots of failures are to be expected (new input syntax, new
> > command line options, new message format, etc).
> > You should run 'make' before 'make check' - that way bison 
> 1.875 gets
> > built, and tests will be run against that instead.  I suppose the
> > rationale here was to allow testing an installed bison; one would
> > normally expect 'make check' to build the application to test before
> > starting the tests.