OpenEuphoria

Re: OpenWatcom 1.6 compilation issue for ex.exe

• Posted by CChris <christian.cuvier at agriculture.gouv.?r> Jul 05, 2007
• 591 views

Matt Lewis wrote:
> 
> CChris wrote:
> > 
> > 
> > When trying to create ex.exe under DOS using OW1.6, I get the "matherr"
> > error.
> > Till then, small wonder.
> > 
> > Adding /dEOW to BE_FLAGS had worked well for exw.exe, so I assulmed it would
> > for ex.exe.
> > 
> > So I added the new variable in imake.bat. Compilation goes well. However,
> > the
> > linker now emits hundreds of error messages about undefined symbols in all
> > be_*.obj
> > files. This happens either in my modified dev directory as well as in the
> > original
> > source directiry.
> > 
> > I noticed ifiles.lnk had lines in lower case and other in upper case,
> > contrary
> > to exw.lnk. So I tried capitalising 4-5 lines at the beginning of the file.
> > To no avail.
> > 
> > Any idea?
> 
> I always use the watcom makefile, but I haven't added support (in the
> makefile )for DOS, mainly because I never use DOS.  It shouldn't be too 
> hard to add it, assuming you're familiar with make files.  One trick is 
> figuring out if the translator generates different files for the front 
> end than get generated for windows.  I know that it's different for Windows
> 
> and Linux, but not sure about DOS.
> 
> But if there are additional errors, I don't know what the solution is, since
> I haven't even attempted to build ex.exe with OW1.6.
> 
> Matt

Never mind. 
I found out that my OW files were split between 2 different WATCOM77
directories. Indeed I had tried (at the time of 1.4) installing the Fortran
compiler as well out of curiosity. And I discovered that this had caused a
thorough mess in some environment variables, leading to a few .lib files not to
be found.

A clean reinstall of OW and a few reboots later, everything is now working
correctly - both ex and exw are correctly output and work as expected.

The curious may now look at http://oedoc.free.fr/get_fixed/ for files where not
only get') and value() return more info, but also the longtime documented quirk
of get() is fixed as well.
Without the fix, the enriched value() and get() can be found at
http://oedoc.free.fr/value_get/ .

Thanks anyway for the quick response.
CChris