1. Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 15, 2008
- 758 views
If you run this simple program it will crash on WIN98.
Note: the d3[1] should have been d[1]
-- junk.ew sequence d d = {1} if d3[1] then puts(1,"error") end if if getc(0) then end if -- end junk.ew
2. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by DerekParnell (admin) Sep 15, 2008
- 763 views
If you run this simple program it will crash on WIN98.
Any chance you can tell us what revision you are using? It's too hard to guess.
Oh, and the error message might be useful too.
3. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 15, 2008
- 805 views
Confirmed with exw and exwc at svn rev 1149 and 1173
Curiously, linux exu at svn rev 1171 doesn't have the issue.
If you run this simple program it will crash on WIN98.
Note: the d3[1] should have been d[1]
-- junk.ew sequence d d = {1} if d3[1] then puts(1,"error") end if if getc(0) then end if -- end junk.ew
4. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 15, 2008
- 761 views
If you run this simple program it will crash on WIN98.
Any chance you can tell us what revision you are using? It's too hard to guess.
Oh, and the error message might be useful too.
I am using svn binaries 1160 with your 1176 include files
because 1160 binaries are the latest available on Jeremy's web site
The win98 system error message is one of those contact your vendor types.
I think is caused by a forward reference scan failure.
Once I corrected the error in my code the program no longer crashes.
The above example is minimal code which create the error.
5. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 15, 2008
- 766 views
Nevermind, somehow my source hadnt updated emit.e (even though it was at rev 1173)
Testing again now...
Confirmed with exw and exwc at svn rev 1149 and 1173
Curiously, linux exu at svn rev 1171 doesn't have the issue.
If you run this simple program it will crash on WIN98.
Note: the d3[1] should have been d[1]
-- junk.ew sequence d d = {1} if d3[1] then puts(1,"error") end if if getc(0) then end if -- end junk.ew
6. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 15, 2008
- 758 views
I am using svn binaries 1160 with your 1176 include files
because 1160 binaries are the latest available on Jeremy's web site
The win98 system error message is one of those contact your vendor types.
I think is caused by a forward reference scan failure.
As you know, this forward reference bug is already fixed in svn. (revision 1174 to be pendantic)
Why are you using 1160 binaries?
7. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 15, 2008
- 806 views
I am using svn binaries 1160 with your 1176 include files
because 1160 binaries are the latest available on Jeremy's web site
The win98 system error message is one of those contact your vendor types.
I think is caused by a forward reference scan failure.
As you know, this forward reference bug is already fixed in svn. (revision 1174 to be pendantic)
Why are you using 1160 binaries?
Because 1160 binaries are the latest WIN98 available on Jeremy's web site.
8. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 15, 2008
- 763 views
Because 1160 binaries are the latest WIN98 available on Jeremy's web site.
Why are you using eubins? Why aren't you building your own binaries, using the tree I posted? (You can keep the source tree up to date using svn also, thus allowing you to pull in future fixes and then build them.)
Jeremy has been somewhat resistant in setting up fully automated eubin builds for Windows (since that'd require some sort of virtualization on a linux server in order to run unit tests), so windows users are probably best off building their own binaries until a stable release is made.
9. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 15, 2008
- 764 views
Because 1160 binaries are the latest WIN98 available on Jeremy's web site.
Why are you using eubins? Why aren't you building your own binaries, using the tree I posted? (You can keep the source tree up to date using svn also, thus allowing you to pull in future fixes and then build them.)
Jeremy has been somewhat resistant in setting up fully automated eubin builds for Windows (since that'd require some sort of virtualization on a linux server in order to run unit tests), so windows users are probably best off building their own binaries until a stable release is made.
1. What version of Watcom do I use 11.c or the new beta ver. of Watcom ?
2. Can I build Euphoria using any old version of the binaries ?
3. What special requirements are needed when building WIN98 binaries ?
Jeremy said something was different when building WIN98.
I already have a SVN Client.
10. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 15, 2008
- 816 views
1. What version of Watcom do I use 11.c or the new beta ver. of Watcom ?
OpenWatcom 1.7a - at least that is what I use.
There are some small differences between Watcom and OpenWatcom (hence the special EOW macro). Watcom 11.c should work also, but I have not tried it.
2. Can I build Euphoria using any old version of the binaries ?
No, however the 1160 binaries should be able to build current svn. Same as the 1173 binaries that I included in the source directory of the svn tree.
Note that once you are building your own binaries, you need to track svn closely in order to make sure that your binaries and svn stay up to date (i.e. rebuild the binaries often).
3. What special requirements are needed when building WIN98 binaries ?
Jeremy said something was different when building WIN98.
Edit config.wat and add "MANAGED_MEM=1" on its own line, no whitespace in front of it. This is the only difference.
11. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by ne1uno Sep 15, 2008
- 886 views
3. What special requirements are needed when building WIN98 binaries ?
Jeremy said something was different when building WIN98.
Edit config.wat and add "MANAGED_MEM=1" on its own line, no whitespace in front of it. This is the only difference.
heres a few more details include in your path= a path to eu4/bin and have a recent version of exwc.exe installed there. cd eu4/source ed makefile.wat EXE=set EUINC=$(PWD)\..\include && $(EX) #EXE=$(EX) change to #EXE=set EUINC=$(PWD)\..\include && $(EX) EXE=$(EX) run configure.bat to make the copies of the obj distribution files then edit config.wat which configure.bat creates but doesn't work well on win9x add PWD=path to your source dir MANAGED_MEM=1 wmake -f makefile.wat winall I think a few tests are still failing or hanging but this is how to run the windows tests. wmake -f makefile.wat testwin executables will be in the source directory you can copy them to the bin directory now.
12. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 15, 2008
- 816 views
- Last edited Sep 16, 2008
etc.
Thank You Very much Jim !
I set-up Watcom and Euphoria on my WIN2000 system and
the instructions you gave me enabled me to compile some new exe files.
I only have one problem when I execute the exw.exe the version number
shows as ' SVN Revision ??? ' with no number just 3 ???
Where does the compile pick-up the SVN number from.
13. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 15, 2008
- 802 views
- Last edited Sep 16, 2008
Thank You Very much Jim !
I set-up Watcom and Euphoria on my WIN2000 system and
the instructions you gave me enabled me to compile some new exe files.
np, btw ne1uno was able to build binaries directly on windows 98.
I only have one problem when I execute the exw.exe the version number
shows as ' SVN Revision ??? ' with no number just 3 ???
Where does the compile pick-up the SVN number from.
Can't find ../.svn/entries or ../svn~1/entries
This is not a big deal, as long as the binaries work.
14. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by mattlewis (admin) Sep 16, 2008
- 756 views
I only have one problem when I execute the exw.exe the version number shows as ' SVN Revision ??? ' with no number just 3 ??? Where does the compile pick-up the SVN number from.
Can't find ../.svn/entries or ../svn~1/entries
This is not a big deal, as long as the binaries work.
Jim's referring to the svn metadata. Did you do a checkout or an export? An export doesn't create the svn metadata for you, which means that it can't automatically put the svn revision number into rev.e. You can do that manually, though.
Matt
15. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 16, 2008
- 791 views
Jim's referring to the svn metadata. Did you do a checkout or an export? An export doesn't create the svn metadata for you, which means that it can't automatically put the svn revision number into rev.e. You can do that manually, though.
Matt:
I did an export.
If I do a checkout; can I do a compile on it even though I have
a directory full of the svn metadata ?
Can I still have the 3.1 include files in the SVN checkout directory ?
Is there any thing I have to be carefull about if I do an update SVN
rather than an checkout.
16. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by jimcbrown (admin) Sep 16, 2008
- 745 views
I did an export.
Which explains the ???.
If I do a checkout; can I do a compile on it even though I have
a directory full of the svn metadata ?
This is the intended usage for developers. Other than revget.ex, the svn metadata is ignored by the build process.
Can I still have the 3.1 include files in the SVN checkout directory ?
Yes, although for now you'll have to copy them over manually. But once copied, svn will ignore them. (At least until we make a final release and add back in the 3.1 includes into the release.)
So, you should be able to do this without issues, as long as you leave the std/ include files alone.
Is there any thing I have to be carefull about if I do an update SVN
rather than an checkout.
You need a checkout the first time. Then you should use svn update to keep the checkout up to date with svn HEAD. Unless you are a developer or otherwise actively modifying source code for the interpreter or the build process, you shouldn't have to care.
17. Re: Ver 4.0 Another WIN98 parsing crash
- Posted by bernie Sep 16, 2008
- 752 views
etc.
Thanks Jim and Matt !
