Re: [Flex-help] flex-2.5.37 Tests FAILED: 48

[Will E. <wes...@gm...>]

On Wednesday, 24 October 2012,  3:40 am -0400, Dennis Clarke <dc...@bl...> wrote:

> turns out the issue was in the flex "tests" Makefiles which were all missing the $CXXFLAGS env var in the compile stage and thus we got 32-bit ELF objects out when 64-bit were required. 

$(CXXFLAGS) should only be used for c++ specific options, which would
only kill a couple of tests.

If you'd submit your patch, I'd look at what you did for inclusion in
the flex code base.

You can build flex without bison from the source distribution sdince
that includes all the built flex and bison files. It's just the test
suite that expects tools to already exist. So there's your bootstrap
path: building once without testing. Then rebuilding with testing.



> 
> trivial to fix and then: 
> 
> 
> echo Results: ; \
> echo Tests succeeded: `echo  "$NOK\c"|wc -c`; \
> echo Tests FAILED: `echo  "$NFAIL\c"|wc -c` ; \
> test "$NFAIL" = ""
> Executing test test-concatenated-options
> Test test-concatenated-options succeeded.
> Executing test test-c++-yywrap
> Test test-c++-yywrap succeeded.
> Executing test test-extended
> Test test-extended succeeded.
> Executing test test-ccl
> Test test-ccl succeeded.
> Executing test test-quotes
> Test test-quotes succeeded.
> Executing test test-rescan-r
> Test test-rescan-r succeeded.
> Executing test test-rescan-nr
> Test test-rescan-nr succeeded.
> Executing test test-basic-nr
> Test test-basic-nr succeeded.
> Executing test test-basic-r
> Test test-basic-r succeeded.
> Executing test test-bison-yylloc
> Test test-bison-yylloc FAILED. See test-bison-yylloc/OUTPUT for details.
> Executing test test-bison-yylval
> Test test-bison-yylval FAILED. See test-bison-yylval/OUTPUT for details.
> Executing test test-bison-nr
> Test test-bison-nr FAILED. See test-bison-nr/OUTPUT for details.
> Executing test test-multiple-scanners-nr
> Test test-multiple-scanners-nr succeeded.
> Executing test test-multiple-scanners-r
> Test test-multiple-scanners-r succeeded.
> Executing test test-header-nr
> Test test-header-nr succeeded.
> Executing test test-header-r
> Test test-header-r succeeded.
> Executing test test-reject
> Test test-reject succeeded.
> Executing test test-c++-multiple-scanners
> Test test-c++-multiple-scanners succeeded.
> Executing test test-c++-basic
> Test test-c++-basic succeeded.
> Executing test test-posixly-correct
> Test test-posixly-correct succeeded.
> Executing test test-posix
> Test test-posix succeeded.
> Executing test test-mem-r
> Test test-mem-r succeeded.
> Executing test test-mem-nr
> Test test-mem-nr succeeded.
> Executing test test-debug-nr
> Test test-debug-nr succeeded.
> Executing test test-debug-r
> Test test-debug-r succeeded.
> Executing test test-lineno-r
> Test test-lineno-r succeeded.
> Executing test test-lineno-nr
> Test test-lineno-nr succeeded.
> Executing test test-linedir-r
> Test test-linedir-r succeeded.
> Executing test test-array-nr
> Test test-array-nr succeeded.
> Executing test test-array-r
> Test test-array-r succeeded.
> Executing test test-c-cpp-nr
> Test test-c-cpp-nr succeeded.
> Executing test test-c-cpp-r
> Test test-c-cpp-r succeeded.
> Executing test test-include-by-buffer
> Test test-include-by-buffer succeeded.
> Executing test test-include-by-push
> Test test-include-by-push succeeded.
> Executing test test-include-by-reentrant
> Test test-include-by-reentrant succeeded.
> Executing test test-prefix-nr
> Test test-prefix-nr succeeded.
> Executing test test-prefix-r
> Test test-prefix-r succeeded.
> Executing test test-pthread
> Test test-pthread succeeded.
> Executing test test-string-nr
> Test test-string-nr succeeded.
> Executing test test-string-r
> Test test-string-r succeeded.
> Executing test test-yyextra
> Test test-yyextra succeeded.
> Executing test test-alloc-extra
> Test test-alloc-extra succeeded.
> Executing test test-noansi-nr
> Test test-noansi-nr succeeded.
> Executing test test-noansi-r
> Test test-noansi-r succeeded.
> Executing test test-top
> Test test-top succeeded.
> Executing test test-table-opts
> Test test-table-opts succeeded.
> Results:
> Tests succeeded: 46
> Tests FAILED: 6
> gmake[4]: *** [check-local] Error 1
> gmake[4]: Leaving directory `/usr/local/build/flex-2.5.37_SunOS5.10_sparcv9_64-bit/tests'
> gmake[3]: *** [check-am] Error 2
> gmake[3]: Leaving directory `/usr/local/build/flex-2.5.37_SunOS5.10_sparcv9_64-bit/tests'
> gmake[2]: *** [check-recursive] Error 1
> gmake[2]: Leaving directory `/usr/local/build/flex-2.5.37_SunOS5.10_sparcv9_64-bit/tests'
> gmake[1]: *** [check-recursive] Error 1
> gmake[1]: Leaving directory `/usr/local/build/flex-2.5.37_SunOS5.10_sparcv9_64-bit'
> gmake: *** [check] Error 2
> $
> 
> 
> well duh
> 
> $ cat tests/test-bison-yylloc/OUTPUT
> gmake[5]: Entering directory `/usr/local/build/flex-2.5.37_SunOS5.10_sparcv9_64-bit/tests/test-bison-yylloc'
> ../../flex scanner.l
> bison --defines --output=parser.c --name-prefix="test" parser.y
> /bin/bash: bison: command not found
> gmake[5]: *** [parser.c] Error 127
> gmake[5]: Leaving directory `/usr/local/build/flex-2.5.37_SunOS5.10_sparcv9_64-bit/tests/test-bison-yylloc'
> $ 
> 
> bison doesn't bloody exist yet because of circular depend and thus we just proceed at this point and then build bison and then come back and build flex ( again ) and the whole world smiles 
> 
> Dennis 
> 

-- 
Will Estes (wl...@us...)
Flex Project Maintainer
http://flex.sourceforge.net/