Install Bison Flex Cygwin

Installing and Updating Cygwin Packages Installing and Updating Cygwin for 64-bit versions of Windows. Run setup-x86_64.exe any time you want to update or install a Cygwin package for 64-bit windows. The signature for setup-x86_64.exe can be used to verify the validity of this binary using this public key. Installing and Updating Cygwin. Install Cygwin. Make sure you get flex & bison when selecting the packages to install. Make sure you get flex & bison when selecting the packages to install. (Just re-run setup if you miss them the first time around.).

The first step would be to integrate the test suites back and everything that is necessary to execute them. With bison this should be quite easy: just add the testsuite and a created atlocal script (with bison script incorporated if needed). Then all that is likely needed is a minimal MinGW/Cygwin installation + diff to execute it.

Flex seems to be a little bit more work as it doesn't use a autotest testsuite script but a self-made one based on automake. But this may also allow to run the tests with VS nmake (no unix shell interpreter needed). With something important as the parser/tokenizer core of many systems I actually do wander why there are no tests (or did I missed something other that 'the un-modified versions are tested already'). With something important as the parser/tokenizer core of many systems I actually do wander why there are no tests (or did I missed something other that 'the un-modified versions are tested already'). It's all about time and efforts vs results. I only had time to refactor flex/bison code to windows environment. As windows supports linux subsystem I hope this project will be less demanded in the future.

So I don't see any reason to make this project better as it's now. But if you prefer to invest in this I think it would be valuable for the project. Then all that is likely needed is a minimal MinGW/Cygwin installation + diff to execute it.

Is any chance to stay within VS C compiler? With something important as the parser/tokenizer core of many systems I actually do wander why there are no tests (or did I missed something other that 'the un-modified versions are tested already'). It's all about time and efforts vs results. I only had time to refactor flex/bison code to windows environment. As windows supports linux subsystem I hope this project will be less demanded in the future. So I don't see any reason to make this project better as it's now. But if you prefer to invest in this I think it would be valuable for the project.

Then all that is likely needed is a minimal MinGW/Cygwin installation + diff to execute it. Is any chance to stay within VS C compiler? As windows supports linux subsystem I hope this project will be less demanded in the future. I don't see this.

I guess you speak about the so-called 'bash on windows' but this means to install some GB just to translate bison/flex sources to C. Then all that is likely needed is a minimal MinGW/Cygwin installation + diff to execute it. Is any chance to stay within VS C compiler?

Depends on what you understand as 'stay within'. Doing the tests from VS would mean to rewrite the complete testsuite script as VS test (the 'sources' for the testsuite are available, therefore this would be possible but likely time intensive remark: I don't know very much about the VS internal test option).

Otherwise you need something that can execute the test script (= a shell interpreter and some standard tools like diff) or which would be the best option but I haven't heard of any general purpose tool that works create/use a test runner that directly executes the test definitions.a (or an automated tool/script that change these to VS tests)). Note: Even with a MinGW/cygwin shell executing the tests these would still be executed using the VS-generated winflex and winbison executables and would use cl.exe to compile their results. As windows supports linux subsystem I hope this project will be less demanded in the future.

I don't see this. I guess you speak about the so-called 'bash on windows' but this means to install some GB just to translate bison/flex sources to C. Then all that is likely needed is a minimal MinGW/Cygwin installation + diff to execute it. Is any chance to stay within VS C compiler? Depends on what you understand as 'stay within'. Doing the tests from VS would mean to rewrite the complete testsuite script as VS test (the 'sources' for the testsuite are available, therefore this would be possible but likely time intensive remark: I don't know very much about the VS internal test option). Otherwise you need something that can execute the test script (= a shell interpreter and some standard tools like diff) or which would be the best option but I haven't heard of any general purpose tool that works create/use a test runner that directly executes the test definitions.a (or an automated tool/script that change these to VS tests)).

Note: Even with a MinGW/cygwin shell executing the tests these would still be executed using the VS-generated winflex and winbison executables and would use cl.exe to compile their results. I don't see this. I guess you speak about the so-called 'bash on windows' but this means to install some GB just to translate bison/flex sources to C. I meant Doing the tests from VS would mean to rewrite the complete testsuite script as VS test (the 'sources' for the testsuite are available, therefore this would be possible but likely time intensive remark: I don't know very much about the VS internal test option).

I think it's not an option. As I understand is pretty similar to MinGW/cygwin. So we could adopt tests to run using MinGW/cygwin and get possibility to run test under WindowsSubsystemforLinux for free. So user will have two options for tests. Note: Even with a MinGW/cygwin shell executing the tests these would still be executed using the VS-generated winflex and winbison executables and would use cl.exe to compile their results. I understand that. I don't see this.

I guess you speak about the so-called 'bash on windows' but this means to install some GB just to translate bison/flex sources to C. I meant Doing the tests from VS would mean to rewrite the complete testsuite script as VS test (the 'sources' for the testsuite are available, therefore this would be possible but likely time intensive remark: I don't know very much about the VS internal test option). I think it's not an option. As I understand is pretty similar to MinGW/cygwin. So we could adopt tests to run using MinGW/cygwin and get possibility to run test under WindowsSubsystemforLinux for free. So user will have two options for tests. Note: Even with a MinGW/cygwin shell executing the tests these would still be executed using the VS-generated winflex and winbison executables and would use cl.exe to compile their results.

I understand that. If it isn't possible to add the full tests soon we should at least add an example compilation. Thanks to we have a working CI build now which would do the checks, too. Actually the bug I've fixed with is now many years old and would have raised a broken test in the debug environments (it likely had no actual bad result in production but could be seen directly after the commit). I should investigate adding the original test suites with the goal to run them on CI. If this isn't possible within a reasonable time frame I go with extracting bison/flex sources and all needed files to compile them from GnuCOBOL, run bison/flex and try to use the C compiler to compile to object files.

This would at least provide some general checks. Any thoughts about adding a test subfolder containing these files? If it isn't possible to add the full tests soon we should at least add an example compilation. Thanks to we have a working CI build now which would do the checks, too. Actually the bug I've fixed with is now many years old and would have raised a broken test in the debug environments (it likely had no actual bad result in production but could be seen directly after the commit).

1930 buick serial numbers. I should investigate adding the original test suites with the goal to run them on CI. Download lagu ost the heirs love is the moment. If this isn't possible within a reasonable time frame I go with extracting bison/flex sources and all needed files to compile them from GnuCOBOL, run bison/flex and try to use the C compiler to compile to object files. This would at least provide some general checks. Any thoughts about adding a test subfolder containing these files? The first approach to just use the 2.6.4 tests with a hand-revised Makefile and testsuite runner did not work out completely (compilation of the test programs in Release mode is fine but the tests aren't all run) and showed some errors. FLEXVER=2.6.4 wget $FLEXVER/flex- $FLEXVER.tar.gz tar -xvf flex- $FLEXVER.tar.gz cd flex- $FLEXVER./configure cd tests sed -i -e 's /dev/null /NUL ' options.cn make check 'CC=./clwrap.sh ' 'CXX=./clwrap.sh -EHsc ' 'OBJEXT=obj ' 'FLEX=/cygdrive/c/projects/winflexbison/build/winflexbison- $APPVEYORREPOTAGNAME/winflex.exe ' 'YACC=/cygdrive/c/projects/winflexbison/build/winflexbison- $APPVEYORREPOTAGNAME/winbison.exe -y ' Opinions?

Can you please have a look at the currently failing tableopts tests (inspecting the posted test-suite.log)? The first approach to just use the 2.6.4 tests with a hand-revised Makefile and testsuite runner did not work out completely (compilation of the test programs in Release mode is fine but the tests aren't all run) and showed some errors. FLEXVER=2.6.4 wget $FLEXVER/flex- $FLEXVER.tar.gz tar -xvf flex- $FLEXVER.tar.gz cd flex- $FLEXVER./configure cd tests sed -i -e 's /dev/null /NUL ' options.cn make check 'CC=./clwrap.sh ' 'CXX=./clwrap.sh -EHsc ' 'OBJEXT=obj ' 'FLEX=/cygdrive/c/projects/winflexbison/build/winflexbison- $APPVEYORREPOTAGNAME/winflex.exe ' 'YACC=/cygdrive/c/projects/winflexbison/build/winflexbison- $APPVEYORREPOTAGNAME/winbison.exe -y ' Opinions? Can you please have a look at the currently failing tableopts tests (inspecting the posted test-suite.log)?

Winflex.exe -unsafe-no-m4-sect3-escape -tables-file= 'tableoptssernr-Ca.ser.tables ' -tables-verify -o tableoptssernr-Ca.ser.c tableopts.l4 rem change generated C file: comment config.h, replace with cl.exe -DTESTHASTABLESEXTERNAL -DYYNOUNISTDH tableoptssernr-Ca.ser.c Ws232.lib. Tableoptssernr-Ca.ser.exe tableoptssernr-Ca.ser.tables tables verification failed at flexint8t I have not used generation of a tables file before this one and I have no clue how they should work, but I guess the testsuite checks that the result has an errorlevel of zero. If something is unclear or if you need more information I'd recommend to ask in the flex mailing list / flex Github issues. Winflex.exe -unsafe-no-m4-sect3-escape -tables-file= 'tableoptssernr-Ca.ser.tables ' -tables-verify -o tableoptssernr-Ca.ser.c tableopts.l4 rem change generated C file: comment config.h, replace with cl.exe -DTESTHASTABLESEXTERNAL -DYYNOUNISTDH tableoptssernr-Ca.ser.c Ws232.lib. Tableoptssernr-Ca.ser.exe tableoptssernr-Ca.ser.tables tables verification failed at flexint8t I have not used generation of a tables file before this one and I have no clue how they should work, but I guess the testsuite checks that the result has an errorlevel of zero.

If something is unclear or if you need more information I'd recommend to ask in the flex mailing list / flex Github issues.