1. ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 808 views
Congratulations you did it again.
How is a user going to build the latest binaries without the latest binaries ?
I downloaded the latest alpha; but the binaries in that use the old name.
I tried using the latest SVN and renamed the binaries to new name but that doesn't work.
No matter what I try I get the following:
<quote screen>
wmake -h -f makefile.wat E:\dummey\source\intobj\main-.c EX=e:\dummey\bin\eui.ex e EU_TARGET=int. OBJDIR=intobj DEBUG= MANAGED_MEM=1 CONFIG=config.wat DEBUG= MAN AGED_MEM=1 mkdir E:\dummey\source\intobj mkdir E:\dummey\source\intobj\back del /Q E:\dummey\source\intobj\back\*.* del /Q E:\dummey\source\intobj\*.* cd E:\dummey\source\intobj e:\dummey\bin\eui.exe -i E:\dummey\include E:\dummey\source\ec.ex -wat -plat WI N -D EU_MANAGED_MEM -i E:\dummey\include E:\dummey\source\int.ex E:\dummey\source\c_decl.e:985 in procedure version() not enough values to print in sprintf() ... called from E:\dummey\source\compile.e:6822 in procedure BackEnd() ... called from E:\dummey\source\main.e:201 in procedure main() ... called from E:\dummey\source\main.e:212 --> See ex.err Press Enter...</quote>
2. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 08, 2009
- 807 views
Congratulations you did it again.
Again, I want to say, this is alpha software, this is not a maybe things will break, this is things will break. Now, please refer to the post:
Executable Name Changes in SVN rev 1709 and 1713.
Specifically the line that starts with bold text: NOTE: If you are building from SVN revisions, when you upgrade to 1709, in order to build, you must rename your existing exwc.exe file to eui.exe.
Jeremy
3. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 796 views
Congratulations you did it again.
Again, I want to say, this is alpha software, this is not a maybe things will break, this is things will break. Now, please refer to the post:
Executable Name Changes in SVN rev 1709 and 1713.
Specifically the line that starts with bold text: NOTE: If you are building from SVN revisions, when you upgrade to 1709, in order to build, you must rename your existing exwc.exe file to eui.exe.
Jeremy
Why did this mention two SVN and then just say to change one filename in one SVN ?
When do the other names have to be changed ?
What do you have to change when you transition from SVN 1709 to SVN 1713 ?
What do you have to change to transition from SVN 1713 to higher SVNs ?
What are you going to do about running the code in the archive ?
4. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 08, 2009
- 832 views
Why did this mention two SVN and then just say to change one filename in one SVN ?
In 1709 the Windows build changed, I then had to work on the unix builds. They were finally changed in 1713. I forgot to mention in that post that if you are building a unix target from SVN, then you need to move ecu to eui. That would have happened at 1713.
When do the other names have to be changed ?
No other names need to be changed.
What do you have to change when you transition from SVN 1709 to SVN 1713 ?
What do you have to change to transition from SVN 1713 to higher SVNs ?
Nothing. It was windows change (1709) and unix change (1713).
What are you going to do about running the code in the archive ?
Same it has always been, programs that have a breaking change will need to be updated by their author.
Jeremy
5. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 803 views
Why did this mention two SVN and then just say to change one filename in one SVN ?
In 1709 the Windows build changed, I then had to work on the unix builds. They were finally changed in 1713. I forgot to mention in that post that if you are building a unix target from SVN, then you need to move ecu to eui. That would have happened at 1713.
When do the other names have to be changed ?
No other names need to be changed.
What do you have to change when you transition from SVN 1709 to SVN 1713 ?
What do you have to change to transition from SVN 1713 to higher SVNs ?
Nothing. It was windows change (1709) and unix change (1713).
What are you going to do about running the code in the archive ?
Same it has always been, programs that have a breaking change will need to be updated by their author.
Jeremy
I just built SVN 1700 and that was fine.
I then updated to SVN 1709 and changed exwc.exe file to eui.exe and tried building binaries for SVN 1709 with this error
<quote screen>
tab.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_w.c -fo=E:\dummey\source\intobj\back\be_w.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_socket.c -fo=E:\dummey\source\intobj\back\be_soc ket.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_pcre.c -fo=E:\dummey\source\intobj\back\be_pcre. obj e:\dummey\bin\eui.exe -i ..\include revget.ex revget.ex:58 in function is_current() slice length is less than 0 (-4) ... called from revget.ex:205 in procedure rev_1_4() ... called from revget.ex:259 in procedure rev_1_3() ... called from revget.ex:276 --> See ex.err Press Enter...</quote>
6. Re: ver 4.0 No way to build new binaries
- Posted by jimcbrown (admin) Apr 08, 2009
- 802 views
Weird.
Try updating from 1700 to 1701, then 1701 to 1702, 1702 to 1703, 1703 to 1704, 1704 to 1705, 1705 to 1706, 1706 to 1707, 1707 to 1708, then use 1708 to update to 1709.
I just built SVN 1700 and that was fine.
I then updated to SVN 1709 and changed exwc.exe file to eui.exe and tried building binaries for SVN 1709 with this error
<quote screen>
tab.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_w.c -fo=E:\dummey\source\intobj\back\be_w.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_socket.c -fo=E:\dummey\source\intobj\back\be_soc ket.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_pcre.c -fo=E:\dummey\source\intobj\back\be_pcre. obj e:\dummey\bin\eui.exe -i ..\include revget.ex revget.ex:58 in function is_current() slice length is less than 0 (-4) ... called from revget.ex:205 in procedure rev_1_4() ... called from revget.ex:259 in procedure rev_1_3() ... called from revget.ex:276 --> See ex.err Press Enter...</quote>
Actually it may only be necessary to update to 1705 and then use that to build 1706, then use 1706 to build 1709.
7. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 08, 2009
- 864 views
You could avoid these problems and download an eubin for any platform that Euphoria supports. I do this because sometimes there is a headache that the devs know why (because they were coding it) and it's much easier for users to just grab a binary.
For instance, you could svn up all the way and just grab an eubin. No reason to svn up incrementally.
Jeremy
8. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 803 views
What do I have to do to configure to build WIN98 binaries ????
9. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 08, 2009
- 809 views
What do I have to do to configure to build WIN98 binaries ????
I should build WIN98 binaries by default now.
C:\Euphoria\source > configure.bat C:\Euphoria\source > wmake /f makefile.wat
Should do the trick. Previously, you had to pass to configure.bat but that's default now.
Jeremy
10. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 822 views
What do I have to do to configure to build WIN98 binaries ????
I should build WIN98 binaries by default now.
C:\Euphoria\source > configure.bat C:\Euphoria\source > wmake /f makefile.wat
Should do the trick. Previously, you had to pass to configure.bat but that's default now.
Jeremy
Then if you build XP binaries I have to use no-managed-mem ?
Will that build the correct XP DOS binary ?
11. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 821 views
I can not build XP BINARIES.
I can only use the DEFAULT method to build the WIN98 version if that is what it does ?
Will someone explain the new configuration file and how the makefile.wat file now works.
What is causing the problem I think is this feature ????
!include $(TRUNKDIR)\source\version.mak
Has any one tried to build the binaries for XP
using the XP OS with WATCOM ?
12. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 08, 2009
- 808 views
I can not build XP BINARIES.
I can only use the DEFAULT method to build the WIN98 version if that is what it does ?
Will someone explain the new configuration file and how the makefile.wat file now works.
What is causing the problem I think is this feature ????
!include $(TRUNKDIR)\source\version.mak
Has any one tried to build the binaries for XP
using the XP OS with WATCOM ?
Bernie, as long as we support Windows 98, we will be building the official binaries with managed memory, even for XP. Binaries with managed memory will run fine on Windows XP. We will only be distributing one binary for Windows platform, not two different ones for Win9x and others for >= WinXP.
What is the problem you are having with version.mak?
Jeremy
13. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 780 views
Bernie, as long as we support Windows 98, we will be building the official binaries with managed memory, even for XP. Binaries with managed memory will run fine on Windows XP. We will only be distributing one binary for Windows platform, not two different ones for Win9x and others for >= WinXP.
What is the problem you are having with version.mak?
Jeremy
I thought you said that you needed different binaries for each OS.
You told me in the past that your memory requirements were different for XP and VISTA so you had to change the way memory was managed.
So now I only need to build one version and you said nothing about that when I was trying to build SVN 1709 and that was because of the problem of trying to build the XP binaries.
Thanks I'll just use the default.
14. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 08, 2009
- 785 views
I thought you said that you needed different binaries for each OS.
You told me in the past that your memory requirements were different for XP and VISTA so you had to change the way memory was managed.
So now I only need to build one version and you said nothing about that when I was trying to build SVN 1709 and that was because of the problem of trying to build the XP binaries.
Thanks I'll just use the default.
Yes, we did in the past. However, after much testing, the speed difference between the two memory systems is not enough to worry about, so instead of causing hassle with having multiple binaries, we decided to make the older, more compatible memory system the default, managed memory. Compiling w/o managed memory (no-managed-memory to configure.bat) will result in binaries that will not run on Windows 98.
BTW... While talking about Windows 98, do you really use Windows 98 still? We have been wondering how many Windows 98 users and DOS users we really have.
Jeremy
15. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 802 views
I thought you said that you needed different binaries for each OS.
You told me in the past that your memory requirements were different for XP and VISTA so you had to change the way memory was managed.
So now I only need to build one version and you said nothing about that when I was trying to build SVN 1709 and that was because of the problem of trying to build the XP binaries.
Thanks I'll just use the default.
Yes, we did in the past. However, after much testing, the speed difference between the two memory systems is not enough to worry about, so instead of causing hassle with having multiple binaries, we decided to make the older, more compatible memory system the default, managed memory. Compiling w/o managed memory (no-managed-memory to configure.bat) will result in binaries that will not run on Windows 98.
BTW... While talking about Windows 98, do you really use Windows 98 still? We have been wondering how many Windows 98 users and DOS users we really have.
Jeremy
Yes I use WIN98, XP, and LINUX because I want my libraries to support all three OSs.
16. Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 09, 2009
- 837 views
Jeremy:
If you had listen to me when I said that I could not
build XP binaries you would have found your error with
the SVNs much faster.
I was correct in reporting my problem; because the problem
was corrected with your changes in SVN 1889.
With this SVN I can build both managed memory and system memory
binaries.
I never report a problem unless they are real problems.
Any binary built some where after SVN 1850 would allow you
you to build binaries but if you tried use those new binaries to
to build the same code again you would get all kinds of errors.
I would suggest anybody upgrading from early SVNs to start
with a SVN 1850 build and then use those binaries to build
SVN 1889 skipping all the SVNs in between.
17. Re: ver 4.0 No way to build new binaries
- Posted by jeremy (admin) Apr 09, 2009
- 802 views
If you had listen to me when I said that I could not build XP binaries you would have found your error with the SVNs much faster.
Yes, I am quick sometimes. Sorry about that.
BTW... It was 1853 that caused the problem.
Jeremy
