1. ver. 4.0 how to build ex.exe

I am trying to build ver 4 ex.exe with djgpp ver 4.23 and
and all I get is errors trying to run djglib and djgex batch file.

There are no instructions in the documents that spell out the steps
to follow in building the exe's. Shouldn't that spelled out in the docs ?

1. What compiler is supposed to be used to build the ex.exe ?

2. Is there any editing that has to be done in any batch file ?
( like those that were required to build exw.exe )

3. Are there any parameters needed on the command line for the batch files ?

new topic     » topic index » view message » categorize

2. Re: ver. 4.0 how to build ex.exe

bernie said...

I am trying to build ver 4 ex.exe with djgpp ver 4.23 and
and all I get is errors trying to run djglib and djgex batch file.

There are no instructions in the documents that spell out the steps
to follow in building the exe's. Shouldn't that spelled out in the docs ?

1. What compiler is supposed to be used to build the ex.exe ?

2. Is there any editing that has to be done in any batch file ?
( like those that were required to build exw.exe )

3. Are there any parameters needed on the command line for the batch files ?

The batch files haven't been maintained. I don't know if anyone has successfully built ex.exe with DJGPP. You can build it with OpenWatcome, using the makefile.wat. Look at the top of the makefile for the various make targets that are available.

Matt

new topic     » goto parent     » topic index » view message » categorize

3. Re: ver. 4.0 how to build ex.exe

mattlewis said...
bernie said...

I am trying to build ver 4 ex.exe with djgpp ver 4.23 and
and all I get is errors trying to run djglib and djgex batch file.

There are no instructions in the documents that spell out the steps
to follow in building the exe's. Shouldn't that spelled out in the docs ?

1. What compiler is supposed to be used to build the ex.exe ?

2. Is there any editing that has to be done in any batch file ?
( like those that were required to build exw.exe )

3. Are there any parameters needed on the command line for the batch files ?

The batch files haven't been maintained. I don't know if anyone has successfully built ex.exe with DJGPP. You can build it with OpenWatcome, using the makefile.wat. Look at the top of the makefile for the various make targets that are available.

Matt:

Using OpenWatcom ver 1.6 does not have a go32.h in it ?
So it will not build DOS ex.exe file ?

Go32 was used by djgpp.

It comes with:
dos4gw.exe
pmodew.exe
dos32a.exe

What version of OpenWatcom is the standard one ?

So what batch file has to be edited to use with the newer watcom ?

new topic     » goto parent     » topic index » view message » categorize

4. Re: ver. 4.0 how to build ex.exe

bernie said...

Using OpenWatcom ver 1.6 does not have a go32.h in it ? So it will not build DOS ex.exe file ?

Go32 was used by djgpp.

It comes with:
dos4gw.exe
pmodew.exe
dos32a.exe

What version of OpenWatcom is the standard one ?

So what batch file has to be edited to use with the newer watcom ?

I'll say it again: Do not use the batch files to build euphoria.

I only ever build DOS by accident, so I've reached the end of my useful knowledge of building DOS binaries. Did you actually try the makefile? It wasn't clear from your message if you did or not.

Matt

new topic     » goto parent     » topic index » view message » categorize

5. Re: ver. 4.0 how to build ex.exe

bernie said...

I am trying to build ver 4 ex.exe with djgpp ver 4.23 and
and all I get is errors trying to run djglib and djgex batch file.

There are no instructions in the documents that spell out the steps
to follow in building the exe's. Shouldn't that spelled out in the docs ?

1. What compiler is supposed to be used to build the ex.exe ?

2. Is there any editing that has to be done in any batch file ?
( like those that were required to build exw.exe )

3. Are there any parameters needed on the command line for the batch files ?

To build with DJGPP, you use the unix makefile (Makefile) and not the batch files.

So under DJGPP it is:

make

Note that for watcom, the command is:

wmake -f makefile.wat dosall

DJGPP building doesn't quite work. A few simple changes to the makefile will allow it to function correctly, however you will need to have echo.exe and basename.exe installed (and your sh.exe should be a bash shell).

new topic     » goto parent     » topic index » view message » categorize

6. Re: ver. 4.0 how to build ex.exe

mattlewis said...
bernie said...

Using OpenWatcom ver 1.6 does not have a go32.h in it ? So it will not build DOS ex.exe file ?

Go32 was used by djgpp.

It comes with:
dos4gw.exe
pmodew.exe
dos32a.exe

What version of OpenWatcom is the standard one ?

So what batch file has to be edited to use with the newer watcom ?

I'll say it again: Do not use the batch files to build euphoria.

I only ever build DOS by accident, so I've reached the end of my useful knowledge of building DOS binaries. Did you actually try the makefile? It wasn't clear from your message if you did or not.

Matt:

Yes I used MAKEFILE.WAT it does not work with OPENWATCOM Ver 11.6
because OPENWATCOM DOES NOT have go32.exe or have a go32.h.
But go32 is used through out the euphoria source code.

new topic     » goto parent     » topic index » view message » categorize

7. Re: ver. 4.0 how to build ex.exe

bernie said...

Matt:

Yes I used MAKEFILE.WAT it does not work with OPENWATCOM Ver 11.6
because OPENWATCOM DOES NOT have go32.exe or have a go32.h.
But go32 is used through out the euphoria source code.

go32 is only used by the DJGPP sections of the euphoria source code.

Note that if you have DJGPP environment variable set, the build process will auto-detect that DJGPP is installed and attempt to do a DJGPP build.

'set DJGPP=' and then try to wmake again.

new topic     » goto parent     » topic index » view message » categorize

8. Re: ver. 4.0 how to build ex.exe

bernie said...

Using OpenWatcom ver 1.6 does not have a go32.h in it ?

So it will not build DOS ex.exe file ?

Yes I used MAKEFILE.WAT it does not work with OPENWATCOM Ver 11.6 because OPENWATCOM DOES NOT have go32.exe or have a go32.h.

But go32 is used through out the euphoria source code.

In the source code one can see this sort of thing...

#	ifdef EDJGPP 
#		include <go32.h> 
#	endif 
... 
#ifdef EDJGPP                        
   if ((unsigned)peek2_addr <= LOW_MEMORY_MAX) 
     top = _farpeekl(_go32_info_block.selector_for_linear_memory,  
          (unsigned)peek2_addr++); 
   else     
#endif 
So therefore if you are getting messages saying you need go32 its because you have the EDJGPP symbol set, and thus it's expecting you to use DJGPP compiler instead of the Watcom one.

I use OpenWatcom v1.7. The batch file that I wrote to compile the systems on my machine is


%echo off 
%echo buildall.bat 
set EDJGPP= 
set ORIGINALWATCOM= 
set EBORLAND= 
set ELCC= 
set EMINGW= 
set EUNIX= 
 
set SRC=C:\Projects\eu_proj\eu40\trunk\source 
set BIN=C:\Projects\eu_proj\eu40\trunk\bin 
set BKUP=C:\backup\eubin 
 
cd %SRC% 
 
wmake -f makefile.wat clean 
wmake -f makefile.wat distclean 
call configure 
wmake -f makefile.wat all 
 
%echo off 
if exist %BIN%\BACKENDD.EXE copy /Y /B %BIN%\BACKENDD.EXE %BKUP%\ 
if exist %BIN%\EC.EXE copy /Y /B %BIN%\EC.EXE %BKUP%\ 
if exist %BIN%\ec.lib copy /Y /B %BIN%\ec.lib %BKUP%\ 
if exist %BIN%\EX.EXE copy /Y /B %BIN%\EX.EXE %BKUP%\ 
if exist %BIN%\backendc.exe copy /Y /B %BIN%\BACKENDC.EXE %BKUP%\ 
if exist %BIN%\backendw.exe copy /Y /B %BIN%\BACKENDW.EXE %BKUP%\ 
if exist %BIN%\ecw.lib copy /Y /B %BIN%\ecw.lib %BKUP%\ 
if exist %BIN%\ecw.exe copy /Y /B %BIN%\ecw.exe %BKUP%\ 
if exist %BIN%\exwc.exe copy /Y /B %BIN%\exwc.exe %BKUP%\ 
if exist %BIN%\exw.exe copy /Y /B %BIN%\exw.exe %BKUP%\ 
 
if exist %SRC%\BACKENDD.EXE move /Y %SRC%\BACKENDD.EXE %BIN%\ 
if exist %SRC%\EC.EXE move /Y %SRC%\EC.EXE %BIN%\ 
if exist %SRC%\ec.lib move /Y %SRC%\ec.lib %BIN%\ 
if exist %SRC%\EX.EXE move /Y %SRC%\EX.EXE %BIN%\ 
if exist %SRC%\backendc.exe move /Y %SRC%\BACKENDC.EXE %BIN%\ 
if exist %SRC%\backendw.exe move /Y %SRC%\BACKENDW.EXE %BIN%\ 
if exist %SRC%\ecw.lib move /Y %SRC%\ecw.lib %BIN%\ 
if exist %SRC%\ecw.exe move /Y %SRC%\ecw.exe %BIN%\ 
if exist %SRC%\exwc.exe move /Y %SRC%\exwc.exe %BIN%\ 
if exist %SRC%\exw.exe move /Y %SRC%\exw.exe %BIN%\ 


You might be able to adapt that for your environment.

new topic     » goto parent     » topic index » view message » categorize

9. Re: ver. 4.0 how to build ex.exe

DerekParnell said...
bernie said...

Using OpenWatcom ver 1.6 does not have a go32.h in it ?

So it will not build DOS ex.exe file ?

Yes I used MAKEFILE.WAT it does not work with OPENWATCOM Ver 11.6 because OPENWATCOM DOES NOT have go32.exe or have a go32.h.

But go32 is used through out the euphoria source code.

In the source code one can see this sort of thing...

#	ifdef EDJGPP 
#		include <go32.h> 
#	endif 
... 
#ifdef EDJGPP                        
   if ((unsigned)peek2_addr <= LOW_MEMORY_MAX) 
     top = _farpeekl(_go32_info_block.selector_for_linear_memory,  
          (unsigned)peek2_addr++); 
   else     
#endif 
So therefore if you are getting messages saying you need go32 its because you have the EDJGPP symbol set, and thus it's expecting you to use DJGPP compiler instead of the Watcom one.

I use OpenWatcom v1.7. The batch file that I wrote to compile the systems on my machine is


%echo off 
%echo buildall.bat 
set EDJGPP= 
set ORIGINALWATCOM= 
set EBORLAND= 
set ELCC= 
set EMINGW= 
set EUNIX= 
 
set SRC=C:\Projects\eu_proj\eu40\trunk\source 
set BIN=C:\Projects\eu_proj\eu40\trunk\bin 
set BKUP=C:\backup\eubin 
 
cd %SRC% 
 
wmake -f makefile.wat clean 
wmake -f makefile.wat distclean 
call configure 
wmake -f makefile.wat all 
 
%echo off 
if exist %BIN%\BACKENDD.EXE copy /Y /B %BIN%\BACKENDD.EXE %BKUP%\ 
if exist %BIN%\EC.EXE copy /Y /B %BIN%\EC.EXE %BKUP%\ 
if exist %BIN%\ec.lib copy /Y /B %BIN%\ec.lib %BKUP%\ 
if exist %BIN%\EX.EXE copy /Y /B %BIN%\EX.EXE %BKUP%\ 
if exist %BIN%\backendc.exe copy /Y /B %BIN%\BACKENDC.EXE %BKUP%\ 
if exist %BIN%\backendw.exe copy /Y /B %BIN%\BACKENDW.EXE %BKUP%\ 
if exist %BIN%\ecw.lib copy /Y /B %BIN%\ecw.lib %BKUP%\ 
if exist %BIN%\ecw.exe copy /Y /B %BIN%\ecw.exe %BKUP%\ 
if exist %BIN%\exwc.exe copy /Y /B %BIN%\exwc.exe %BKUP%\ 
if exist %BIN%\exw.exe copy /Y /B %BIN%\exw.exe %BKUP%\ 
 
if exist %SRC%\BACKENDD.EXE move /Y %SRC%\BACKENDD.EXE %BIN%\ 
if exist %SRC%\EC.EXE move /Y %SRC%\EC.EXE %BIN%\ 
if exist %SRC%\ec.lib move /Y %SRC%\ec.lib %BIN%\ 
if exist %SRC%\EX.EXE move /Y %SRC%\EX.EXE %BIN%\ 
if exist %SRC%\backendc.exe move /Y %SRC%\BACKENDC.EXE %BIN%\ 
if exist %SRC%\backendw.exe move /Y %SRC%\BACKENDW.EXE %BIN%\ 
if exist %SRC%\ecw.lib move /Y %SRC%\ecw.lib %BIN%\ 
if exist %SRC%\ecw.exe move /Y %SRC%\ecw.exe %BIN%\ 
if exist %SRC%\exwc.exe move /Y %SRC%\exwc.exe %BIN%\ 
if exist %SRC%\exw.exe move /Y %SRC%\exw.exe %BIN%\ 


You might be able to adapt that for your environment.

Thank You Derek !
Also Thanks to Jim and Matt

I see why go32.h is not being found by the watcom compiler.

For example you will find in the DOSOBJ directory a file called omemory.c
This file's first line is #include <go32.h> The < > tells the watcom
compiler to look in it's own include directory and of course it's not there.

There are other "C" include files that are doing the samething.

That would work if you are using DJGPP because the go32 files are in the
correct locations.

Derek I will give your batch file a try on win2000; Thanks

new topic     » goto parent     » topic index » view message » categorize

10. Re: ver. 4.0 how to build ex.exe


Does anybody know where Jermey is ?

1. I need to know what OS he was using to build the WIN98 Binaries on.

2. What files he has to EDIT to compile using openwatcom.

3. What order and steps he is using for the compile and any special
batch files he is using.

4. I need to know how his OS environment and Watcom environment are setup.

I am very frustrated trying to do a simple compile of the binaries using
the make file to create the EX.EXE file.

I keep running into problems with compiler trying to use DJGPP when it
should't.

Who knows what else has to be edited to kill the DJGPP problem.

I have no idea what configure.bat is suppose to accomplish it just wipes
outconfig.wat which has to contain MANAGED_MEM=1 and ??

makefile.wat has to be edited and has notes in it that it doesn't work
for WIN98.

It is ridiculous that there SIMPLY is not a WIN98 option built into the
makefile.wat instead of all this editing.

On top of all that the SVN trunk keeps giving me errors while trying
to update or checkout.

new topic     » goto parent     » topic index » view message » categorize

11. Re: ver. 4.0 how to build ex.exe

I can't help you, I'm sorry.

I don't have WIN98 nor DJGPP. I think you are the only one left with that combination.

Is it not possible for you to get a current version of Windows or Watcom?

new topic     » goto parent     » topic index » view message » categorize

12. Re: ver. 4.0 how to build ex.exe

Bernie, check your PATH enviroment value, probably DJGPP binaries are before in the order. To see the current value, type (in a dos command prompt): echo %PATH% To change it temporarily, type: PATH=YOURDIRECTORY/BIN;%PATH% Then, in the same prompt (that's important), try to compile.

new topic     » goto parent     » topic index » view message » categorize

13. Re: ver. 4.0 how to build ex.exe

DerekParnell said...

I can't help you, I'm sorry.

I don't have WIN98 nor DJGPP. I think you are the only one left with that combination.

Is it not possible for you to get a current version of Windows or Watcom?

Hi Derek:

I have win2000, but I am trying to build and test my software to work on
WIN98.

Someone decided that Euphoria memory management had to be improved and
left WIN98 in the dust. ( This was probably so they can use 64-bits ).

Whoever decided to do that, should be responsible to create a makefile
that will still be able to build win98 binaries.

I have been having these problems trying to build WIN98 binaries on
WIN2000.

There are still users out there that use WIN98.

new topic     » goto parent     » topic index » view message » categorize

14. Re: ver. 4.0 how to build ex.exe

bernie said...


Does anybody know where Jermey is ?

1. I need to know what OS he was using to build the WIN98 Binaries on.

2. What files he has to EDIT to compile using openwatcom.

3. What order and steps he is using for the compile and any special
batch files he is using.

4. I need to know how his OS environment and Watcom environment are setup.

I am very frustrated trying to do a simple compile of the binaries using
the make file to create the EX.EXE file.

I keep running into problems with compiler trying to use DJGPP when it
should't.

Who knows what else has to be edited to kill the DJGPP problem.

I have no idea what configure.bat is suppose to accomplish it just wipes
outconfig.wat which has to contain MANAGED_MEM=1 and ??

makefile.wat has to be edited and has notes in it that it doesn't work
for WIN98.

It is ridiculous that there SIMPLY is not a WIN98 option built into the
makefile.wat instead of all this editing.

On top of all that the SVN trunk keeps giving me errors while trying
to update or checkout.

pick a compiler and version. openwatcom 1.5 and 1.7 work here. haven't tried watcom 11 but minGW w/gcc3.4 now works, look up messages on the dev list to see how to compile.

put into your enviornment WATCOM=path to watcom using set= or however that is done on win2k

makefile.wat won't have to be edited unless you are running wmake on win9x.

first run configure then edit config.wat

dosall makes ex.exe and related files winall makes exw & exwc and related files

everyone deals with the sourceforge problems. make sure the url you are using is is https, wait a few minutes a try again, just update one dir at a time, whatever works.

new topic     » goto parent     » topic index » view message » categorize

15. Re: ver. 4.0 how to build ex.exe

ne1uno said...

pick a compiler and version. openwatcom 1.5 and 1.7 work here. haven't tried watcom 11 but minGW w/gcc3.4 now works, look up messages on the dev list to see how to compile.


Where are these messages; on what dev list ?

Will openwatcom 1.6 work ?

ne1uno said...

put into your enviornment WATCOM=path to watcom using set= or however that is done on win2k

makefile.wat won't have to be edited unless you are running wmake on win9x.

ne1uno said...

first run configure then edit config.wat

When I run configure.bat all I get is an empty file
containing ' # Configuration for Watcom ' nothing else.

What options are you suppose to use on configure.bat command line ?

What am I suppose to edit or add ? MANAGED_MEM=1 and what else ?

ne1uno said...

dosall makes ex.exe and related files winall makes exw & exwc and related files

everyone deals with the sourceforge problems. make sure the url you are using is is https, wait a few minutes a try again, just update one dir at a time, whatever works.

new topic     » goto parent     » topic index » view message » categorize

16. Re: ver. 4.0 how to build ex.exe

I did a checkout of SVN 1182

I ran a clean and distclean

I added 1173 binaries to 1182 bin dir

I ran configure.bat and got an empty config.wat

I added MANAGED_MEM=1 to the config.wat file.

I ran wmake -f makefile.wat all

This is the error that occured when the compiler got to
building the DOS ex.exe file.

{{{ wmake -f makefile.wat ex.exe EX=..\bin\ex.exe EU_TARGET=int. OBJDIR=doso bj DEBUG= MANAGED_MEM=1 OS=DOS Open Watcom Make Version 1.6 Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved. Source code is available under the Sybase Open Watcom Public License. See http://www.openwatcom.org/ for details. ..\bin\ex.exe -i ..\include revget.ex wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ .\d osobj\0emory.c -fo=.\dosobj\0emory.obj .\dosobj\0emory.c(2): Error! E1055: Unable to open 'go32.h' Error(E42): Last command making (.\dosobj\0emory.obj) returned a bad status Error(E02): Make execution terminated Error(E42): Last command making (dos) returned a bad status Error(E02): Make execution terminated Error(E42): Last command making (dosall) returned a bad status Error(E02): Make execution terminated Error(E42): Last command making (all) returned a bad status Error(E02): Make execution terminated }}}

new topic     » goto parent     » topic index » view message » categorize

17. Re: ver. 4.0 how to build ex.exe

Bernie, you don't have to put \\ at the end of each line in the forum posts, and especially not on blank lines. A blank line is interpreted as a blank line - no need to have \\ to say its a new line. So I'm just trying to be helpful, but try writing posts without all the \\ tokens.

bernie said...
ne1uno said...

pick a compiler and version. openwatcom 1.5 and 1.7 work here. haven't tried watcom 11 but minGW w/gcc3.4 now works, look up messages on the dev list to see how to compile.

Where are these messages; on what dev list ?

The archive is at http://sourceforge.net/mailarchive/forum.php?forum_name=rapideuphoria-develop

bernie said...

Will openwatcom 1.6 work ?

I don't know. V1.7 does so why not get that?

bernie said...
ne1uno said...

first run configure then edit config.wat

When I run configure.bat all I get is an empty file containing ' # Configuration for Watcom ' nothing else.

What options are you suppose to use on configure.bat command line ?

What am I suppose to edit or add ? MANAGED_MEM=1 and what else ?

You are running the configure.bat correctly. It is creating a correct config.wat file. You do not need to edit anything. According to the DOCUMENTATION inside the makefile.wat file, you need to run the command line ...

wmake -f makefile.wat interpreter MANAGED_MEM=1 

What are the errors you are getting? How are you getting them (what exactly is your command lines, ENVIRONMENT symbols, PATH, pwd, ...)

new topic     » goto parent     » topic index » view message » categorize

18. Re: ver. 4.0 how to build ex.exe

DerekParnell said...

You are running the configure.bat correctly. It is creating a correct config.wat file. You do not need to edit anything. According to the DOCUMENTATION inside the makefile.wat file, you need to run the command line ...

wmake -f makefile.wat interpreter MANAGED_MEM=1

That does not build EX.EXE

DerekParnell said...

What are the errors you are getting? How are you getting them (what exactly is your command lines, ENVIRONMENT symbols, PATH, pwd, ...)

See my previous post that show the errors.

Thanks Derek

new topic     » goto parent     » topic index » view message » categorize

19. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

If a user has a DJGPP compiler on their system and has the enviornment 
variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the 
path. 
 
The makefile for some reason sees it as an option for the compile. 
Maybe it is a bad idea to be using actual compiler names as flags to 
control the actions of the compiler. 
 
Also OpenWatcom Ver 1.6 does work. 
 
Thanks to everyone for all the help. 
Bernie 

new topic     » goto parent     » topic index » view message » categorize

20. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

bernie said...

If a user has a DJGPP compiler on their system and has the enviornment variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the path.

The makefile for some reason sees it as an option for the compile. Maybe it is a bad idea to be using actual compiler names as flags to control the actions of the compiler.

Also OpenWatcom Ver 1.6 does work.

Thanks to everyone for all the help.

Bernie

The problem is coming from InitBackEnd in traninit.e in this if statement:

traninit.e said...
	if TDOS then 
		wat_path = 0 
		if length(compile_dir) then 
			if djg_option then 
				dj_path  = compile_dir 
			else 
				wat_path = compile_dir 
			end if 
			return 
		end if 
			 
		dj_path = getenv("DJGPP") 
		if atom(dj_path) or wat_option then 
			wat_path = getenv("WATCOM") 
			if atom(wat_path) then 
				wat_path = "C:\\WATCOM" 
			end if 
			dj_path = 0 
		end if 
		if djg_option and atom(dj_path) then 
			CompileErr("DJGPP environment variable is not set") 
		end if 
		if wat_option and atom(wat_path) then 
			CompileErr("WATCOM environment variable is not set") 
		end if 
	end if 

We should probably specify the -wat option in makefile.wat. Or possibly revisit the logic above if that's not working correctly.

Matt

new topic     » goto parent     » topic index » view message » categorize

21. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

bernie said...

If a user has a DJGPP compiler on their system and has the enviornment 
variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the 
path. 

Bernie, are you ignoring my posts? I already told you this.

new topic     » goto parent     » topic index » view message » categorize

22. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

jimcbrown said...
bernie said...

If a user has a DJGPP compiler on their system and has the enviornment 
variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the 
path. 

Bernie, are you ignoring my posts? I already told you this.

Then why didn't you correct the error in the code in traninit.e if you knew about it ?

new topic     » goto parent     » topic index » view message » categorize

23. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

bernie said...
jimcbrown said...
bernie said...

If a user has a DJGPP compiler on their system and has the enviornment 
variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the 
path. 

Bernie, are you ignoring my posts? I already told you this.

Then why didn't you correct the error in the code in traninit.e if you knew about it ?

I never had time to investigate it that far, so I didn't know. Sorry.

new topic     » goto parent     » topic index » view message » categorize

24. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

jimcbrown said...
bernie said...
jimcbrown said...
bernie said...

If a user has a DJGPP compiler on their system and has the enviornment 
variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the 
path. 

Bernie, are you ignoring my posts? I already told you this.

Then why didn't you correct the error in the code in traninit.e if you knew about it ?

I never had time to investigate it that far, so I didn't know. Sorry.

Thats ok but if you didn't help me as much as you did I would be still struggling and stumbling along trying to build the binaries.

Thanks again ! Bernie

new topic     » goto parent     » topic index » view message » categorize

25. Re: ver. 4.0 how to build ex.exe FOUND PROBLEM

mattlewis said...
bernie said...

If a user has a DJGPP compiler on their system and has the enviornment variable DJGPP=D:\DJGPP\DJGPP.ENV even though it is not added to the path.

The makefile for some reason sees it as an option for the compile. Maybe it is a bad idea to be using actual compiler names as flags to control the actions of the compiler.

Also OpenWatcom Ver 1.6 does work.

Thanks to everyone for all the help.

Bernie

The problem is coming from InitBackEnd in traninit.e in this if statement:

traninit.e said...
	if TDOS then 
		wat_path = 0 
		if length(compile_dir) then 
			if djg_option then 
				dj_path  = compile_dir 
			else 
				wat_path = compile_dir 
			end if 
			return 
		end if 
			 
		dj_path = getenv("DJGPP") 
		if atom(dj_path) or wat_option then 
			wat_path = getenv("WATCOM") 
			if atom(wat_path) then 
				wat_path = "C:\\WATCOM" 
			end if 
			dj_path = 0 
		end if 
		if djg_option and atom(dj_path) then 
			CompileErr("DJGPP environment variable is not set") 
		end if 
		if wat_option and atom(wat_path) then 
			CompileErr("WATCOM environment variable is not set") 
		end if 
	end if 

We should probably specify the -wat option in makefile.wat. Or possibly revisit the logic above if that's not working correctly.

Matt

Matt, my latest better_build patch does this and it passes -cc -wat to the eutest when running tests, which is passed to the translator in turn. We should specify which compiler we want whenever we make a translation. With my changes the translator will complain if you don't. I posted this on the list weeks ago but it was ignored.

These problems are not new . You will be able to try this patches on Thursday at http://euphoria.blogdns.com/. I haven't uploaded it yet to this server.

In the meantime, checkout the system_exec_withspaces patch and their tests.

Shawn Pringle

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu