1. ver 4.0 SOMETHING is broken in the SVN code
- Posted by bernie Dec 09, 2008
- 1052 views
Well I was told that I should upgrade from win2000 and win98.
So I built a new machine an installed openwatcom 1.7, tortoiseSVN and
installed new XP operating system.
I then did a complete SVN checkout.
Guess what; I still have problems building binaries.
I ran configure with just the eubin directory option.
then wmake -f makefile.wat all
And this is what I get when I get to this section of wmake
if not exist dostrobj mkdir dostrobj if not exist dostrobj\back mkdir dostrobj\back if not exist dosbkobj mkdir dosbkobj if not exist dosbkobj\back mkdir dosbkobj\back wmake -f makefile.wat .\dosobj\main-.c EX="e:\eu_master\bin"\ex.exe EU_T ARGET=int. OBJDIR=dosobj DEBUG= MANAGED_MEM=1 OS=DOS Open Watcom Make Version 1.7 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. cd .\dosobj del *.c Could Not Find E:\eu_master\source\dosobj\*.c e:\eu_master\bin\ex.exe -i ..\..\include ..\ec.ex -i ..\..\include ..\i nt.ex Error(E14): Cannot execute (e:\eu_master\bin\ex.exe): No such file or directory Error(E42): Last command making (.\dosobj\main-.c) 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 Press any key to continue . . .
Will some developer do a COMPLETE fresh SVN checkout WITHOUT adding any other files
and use the makefile.wat to see if they can build the binaries with XP.
The dosobj files are missing they are not being built or are being deleted by
something. It is impossible me for me to guess what is be done by this make
file so I need help by the original author of the makefile.wat
PS: Don't tell me that I need VISTA because I'am on a fixed income.
2. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by jimcbrown (admin) Dec 09, 2008
- 1061 views
Well I was told that I should upgrade from win2000 and win98.
So I built a new machine an installed openwatcom 1.7, tortoiseSVN and
installed new XP operating system.
I wasn't aware that the build process had broke on w98.
I then did a complete SVN checkout.
Guess what; I still have problems building binaries.
Could Not Find E:\eu_master\source\dosobj\*.c e:\eu_master\bin\ex.exe -i ..\..\include ..\ec.ex -i ..\..\include ..\i nt.ex Error(E14): Cannot execute (e:\eu_master\bin\ex.exe): No such file or directory
Will some developer do a COMPLETE fresh SVN checkout WITHOUT adding any other files
and use the makefile.wat to see if they can build the binaries with XP.
The dosobj files are missing they are not being built or are being deleted by
something. It is impossible me for me to guess what is be done by this make
file so I need help by the original author of the makefile.wat
The problem isn't the missing *.c files in dosobj.
The problem is the missing ex.exe
Double check to see if you have ex.exe in your eubins in the right place.
If you do not have an ex.exe in eubins and you can not find one, do this:
wmake -f makefile.wat eubin copy ex.exe c:\eu_master\bin
And then run the entire build again.
PS: Don't tell me that I need VISTA because I'am on a fixed income.
Ok, you don't need VISTA. ex.exe doesn't work on VISTA anyways, you can't build ex.exe on VISTA (or any of dosobj) without some special hacks.
3. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by mattlewis (admin) Dec 09, 2008
- 1024 views
Well I was told that I should upgrade from win2000 and win98.
So I built a new machine an installed openwatcom 1.7, tortoiseSVN and
installed new XP operating system.
I then did a complete SVN checkout.
Guess what; I still have problems building binaries.
I ran configure with just the eubin directory option.
then wmake -f makefile.wat all
And this is what I get when I get to this section of wmake
Error(E14): Cannot execute (e:\eu_master\bin\ex.exe): No such file or directory
Here's the problem. It looks like that file isn't where you said it was. What happens when you run (from the command line):
> e:\eu_master\bin\ex.exe
Matt
4. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by bernie Dec 09, 2008
- 1068 views
Here's the problem. It looks like that file isn't where you said it was. What happens when you run (from the command line):
> e:\eu_master\bin\ex.exe
Matt
Matt:
When I copied the binaries over to my bin directory ex.exe didn't get
copied over for some reason.
After copying ex into bin and running again I get the following error.
wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_callc.c -fo=.\dosobj\back\be_callc.obj wcc386 /oe=40 /ol /dEDOS /dEWATCOM /dEOW /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ be_inline.c -fo=.\dosobj\back\be_inline.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_machine.c -fo=.\dosobj\back\be_machine.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_rterror.c -fo=.\dosobj\back\be_rterror.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_syncolor.c -fo=.\dosobj\back\be_syncolor.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_runtime.c -fo=.\dosobj\back\be_runtime.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_symtab.c -fo=.\dosobj\back\be_symtab.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_w.c -fo=.\dosobj\back\be_w.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_regex.c -fo=.\dosobj\back\be_regex.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW regex.c -fo=.\dosobj\back\regex.obj wlink @.\dosobj\ex.lbc name ex.exe le23p ex.exe Error(E14): Cannot execute (le23p): No such file or directory Error(E42): Last command making (ex.exe) returned a bad status Should this file be deleted [Yes/No] ?
Where is this looking for le23p ??
5. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by mattlewis (admin) Dec 09, 2008
- 1018 views
When I copied the binaries over to my bin directory ex.exe didn't get
copied over for some reason.
After copying ex into bin and running again I get the following error.
le23p ex.exe Error(E14): Cannot execute (le23p): No such file or directory
Where is this looking for le23p ??
Looks like it's part of Causeway. It should be in the bin directory of the trunk. There are two files (le23.exe and cwc.exe) that the makefile executes apparently to link the Causeway stuff. When I run them alone, I get:
LE to 3P Converter v2.02 Copyright 1994-96 Michael Devore; all rights reserved. CauseWay Compressor 3.01 Copyright 1993-96 Michael Devore; all rights reserved.Try adding them to your path. I never build the DOS stuff, so that's the limit of my knowledge.
Matt
6. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by bernie Dec 09, 2008
- 1041 views
Looks like it's part of Causeway. It should be in the bin directory of the trunk. There are two files (le23.exe and cwc.exe) that the makefile executes apparently to link the Causeway stuff. When I run them alone, I get:
LE to 3P Converter v2.02 Copyright 1994-96 Michael Devore; all rights reserved. CauseWay Compressor 3.01 Copyright 1993-96 Michael Devore; all rights reserved.Try adding them to your path. I never build the DOS stuff, so that's the limit of my knowledge.
Matt
They are there
I tried using just DOSALL option but that gives same error.
I can not believe that there is no one building DOS binaries
without any problem.
How is any testing be done on DOS programs ??
7. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by mattlewis (admin) Dec 09, 2008
- 1034 views
Try adding them to your path. I never build the DOS stuff, so that's the limit of my knowledge.
They are there
I tried using just DOSALL option but that gives same error.
I can not believe that there is no one building DOS binaries
without any problem.
How is any testing be done on DOS programs ??
When you say "they are all there," do you mean they're in that directory, or in your path? If they're in your path and you're getting the 'not found' errors, then you have bigger problems than building euphoria.
I'm not sure that there is anyone really actively developing/testing for DOS. For myself, working both Windows and Linux stretches me pretty thin. Anyway, it's probably incorrect to project your difficulty in configuring your system.
However, it does point out that we could do with some better documentation. I thought there was a wiki page on how to build 4.0, but now I can't find it.
Matt
8. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by DerekParnell (admin) Dec 09, 2008
- 1105 views
Looks like it's part of Causeway. It should be in the bin directory of the trunk. There are two files (le23.exe and cwc.exe) that the makefile executes apparently to link the Causeway stuff. When I run them alone, I get:
LE to 3P Converter v2.02 Copyright 1994-96 Michael Devore; all rights reserved. CauseWay Compressor 3.01 Copyright 1993-96 Michael Devore; all rights reserved.Try adding them to your path. I never build the DOS stuff, so that's the limit of my knowledge.
Matt
They are there
I tried using just DOSALL option but that gives same error.
I can not believe that there is no one building DOS binaries
without any problem.
How is any testing be done on DOS programs ??
I build the DOS binaries everytime I build Euphoria. I DO NOT HAVE A SINGLE PROBLEM!
The message you are getting "Cannot execute (le23p): No such file or directory " tells you something, no?
Your problem is that the tools you need are not in your PATH statement. Either the PATH is wrong or the tools are where you said they would be.
What are your PATH, EUDIR, and EUINC symbols set to?
After getting the SVN copy and the latest binaries onto your system, did you make the necessary changes to PATH, EUDIR and EUINC? Also, does INCLUDE contain the Watcom include directories?
The PATH needs to contain the v4 bin directory, and the two Watcom directories .../binnt and .../binw
9. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by DerekParnell (admin) Dec 09, 2008
- 1044 views
However, it does point out that we could do with some better documentation. I thought there was a wiki page on how to build 4.0, but now I can't find it.
I found it ... http://openeuphoria.org/wiki/euwiki.cgi?Compiling40
I'll start bringing it up to date it today.
10. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by bernie Dec 09, 2008
- 1059 views
Looks like it's part of Causeway. It should be in the bin directory of the trunk. There are two files (le23.exe and cwc.exe) that the makefile executes apparently to link the Causeway stuff. When I run them alone, I get:
LE to 3P Converter v2.02 Copyright 1994-96 Michael Devore; all rights reserved. CauseWay Compressor 3.01 Copyright 1993-96 Michael Devore; all rights reserved.Try adding them to your path. I never build the DOS stuff, so that's the limit of my knowledge.
Matt
They are there
I tried using just DOSALL option but that gives same error.
I can not believe that there is no one building DOS binaries
without any problem.
How is any testing be done on DOS programs ??
I build the DOS binaries everytime I build Euphoria. I DO NOT HAVE A SINGLE PROBLEM!
The message you are getting "Cannot execute (le23p): No such file or directory " tells you something, no?
Your problem is that the tools you need are not in your PATH statement. Either the PATH is wrong or the tools are where you said they would be.
What are your PATH, EUDIR, and EUINC symbols set to?
After getting the SVN copy and the latest binaries onto your system, did you make the necessary changes to PATH, EUDIR and EUINC? Also, does INCLUDE contain the Watcom include directories?
The PATH needs to contain the v4 bin directory, and the two Watcom directories .../binnt and .../binw
Thanks Derek and Matt !
Derek was right AGAIN !
I had my path all messed up.
I am just not use to these modern operating systems.
Now if I can only convince Igor to use the makefile.wat
11. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by kinz Dec 10, 2008
- 1027 views
Now if I can only convince Igor to use the makefile.wat
Hi Bernie, I got all dos32 and win32 binaries using
makefile.wat exactly, but I worked with the source
tarball, not with SVN.
So, tarball and SVN are both tested now and work, with
some bugs, but work for users.
Regards,
Igor Kachan
kinz@peterlink.ru
12. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by bernie Dec 10, 2008
- 1059 views
Now if I can only convince Igor to use the makefile.wat
Hi Bernie, I got all dos32 and win32 binaries using
makefile.wat exactly, but I worked with the source
tarball, not with SVN.
So, tarball and SVN are both tested now and work, with
some bugs, but work for users.
Regards,
Igor Kachan
kinz@peterlink.ru
Hi Igor:
You should not get any bugs ?
When you posted that image of your path, I noticed that
you have DJGPP in your path that can cause you a problem
when building binaries if you are setting DJGPP.ENV
It will confuse the makefile.wat and cause errors.
That caused me a lot of problems when I was building
Win98 binaries on my Win 2000 system.
13. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by SDPringle Dec 12, 2008
- 1049 views
Hello Bernie,
Can you try the command line svn program? I do 'svn up' at the command line and it tells me that it doesn't know Equifax. So, I have to just trust the certificate as it is without verification. Which is ridiculous. Equifax is a well known certificate authority. I wonder if this problem is just happening on my system or if it is a global problem only affecting those of who use Windows and DOS.
Shawn Pringle
14. Re: ver 4.0 SOMETHING is broken in the SVN code
- Posted by bernie Dec 12, 2008
- 1025 views
Hello Bernie,
Can you try the command line svn program? I do 'svn up' at the command line and it tells me that it doesn't know Equifax. So, I have to just trust the certificate as it is without verification. Which is ridiculous. Equifax is a well known certificate authority. I wonder if this problem is just happening on my system or if it is a global problem only affecting those of who use Windows and DOS.
Shawn Pringle
Hi Shawn:
I am now using XP for SVN.
When I used Win98 or Win2000; I would get the trust certificate.
I could accept it temporarily or permanently, both would work
but I did get the message. If you have tortiseSVN you don't need to use the command-line
you can just right click on your destination folder and you will
get a context menu that allows you to perform different options.
