OpenEuphoria

2. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by andi49 Jan 16, 2014
• 2567 views

Hallo

Compiling the 64 Bit Version of OpenEuphoria 4.1, from the repo, works only using 64 Bit Euphoria binaries. Is it correct that the current 64 Bit 4.1 Version can't be built with a 32 Bit 4.1 Version? (It was possible before)?
Or is this a failure in my setup?

I'am only asking for the Windows Version.

Andreas

4. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by jimcbrown (admin) Jan 17, 2014
• 2517 views

IIUC, that means there is a regression that needs to be fixed in 4.1

6. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by jimcbrown (admin) Jan 17, 2014
• 2479 views

No, it wasn't.

User supplied library does not exist: 
    c:\eu4neu\euphoria\source\build\eu.a 
 
c:\eu4neu\euphoria\source\scanner.e:1032 in function MakeInt() 
type_check failure, maxchk is 4.611686018e+017 

That's good to hear. Hopefully it's just a config change or missing update that andi49 needs to get 64bit builds going on andi49's box again.

8. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by andi49 Jan 17, 2014
• 2497 views

Hallo

I checked again

C:\>c:\bit\built\4.1-32\bin\eui.exe 
Euphoria Interpreter v4.1.0 development 
   32-bit Windows, Using System Memory 
   Revision Date: 2014-01-11 22:35:01, Id: 6183:944d3dd7b349 
 
ERROR: Must specify the file to be interpreted on the command line 

My Batchfile

call ../../vars64.bat 
make clean 
hg pull 
hg update default 
sh configure --eubin=c:/bit/built/4.1-32/bin  --arch=x86_64   
make 
pause 

The vars64.bat (just set the Path to include the the 64-bit compiler)

set PATH=c:\mingw64\bin;c:\msys\msys\bin;%PATH% 

Result

c:\eu4neu\euphoria\source\scanner.e:1032 in function MakeInt() 
type_check failure, maxchk is 4.611686018e+017 
 
... called from c:\eu4neu\euphoria\source\scanner.e:1770 in function Scanner() 
 
 
... called from c:\eu4neu\euphoria\source\parser.e:720 in function next_token() 
 
 
... called from c:\eu4neu\euphoria\source\parser.e:1359 in procedure UFactor() 
 
 
... called from c:\eu4neu\euphoria\source\parser.e:1383 in function Term() 
 
... called from c:\eu4neu\euphoria\source\parser.e:1398 in function aexpr() 
 
... called from c:\eu4neu\euphoria\source\parser.e:1412 in function cexpr() 
 
... called from c:\eu4neu\euphoria\source\parser.e:1435 in function rexpr() 
 
... called from c:\eu4neu\euphoria\source\parser.e:1474 in procedure Expr() 
 
... called from c:\eu4neu\euphoria\source\parser.e:3570 in function Global_decla 
ration() 
 
... called from c:\eu4neu\euphoria\source\parser.e:4832 in procedure real_parser 
() 
 
... called from c:\eu4neu\euphoria\source\parser.e:5035 in procedure parser() 
 
... called from c:\eu4neu\euphoria\source\main.e:201 in procedure main() 
 
... called from c:\eu4neu\euphoria\source\main.e:228 
 
--> See ex.err 
make[2]: *** [c:/eu4neu/euphoria/source/build/intobj/main-.c] Error 1 
make[2]: Leaving directory `/c/eu4neu/euphoria/source' 
make[1]: *** [interpreter] Error 2 
make[1]: Leaving directory `/c/eu4neu/euphoria/source' 
make: *** [all] Error 2 
 
C:\eu4neu\euphoria\source>pause 

ex.err is here http://euphoria.indonesianet.de/ex.err
(It's about 155KB)

Same procedure with 64bit binaries is working.

Windows 8.1 64bit, TDM GCC 4.7.1

Thank you
Andreas

10. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by andi49 Jan 18, 2014
• 2413 views

Hallo

Yes, seems it works now.

But i also have to declare 'num' (also in function MakeInt()) as an atom.

Thank you

Andreas

12. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by _tom (admin) Jan 24, 2014
• 2207 views

I'll try running your build on a virtual machine. The 32 bit version would be best.

_tom

14. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by Steady Jan 25, 2014
• 2144 views

"some batchfiles to create new builts from the repo"

Myconfig32.bat
Line 1: “call ../vars.bat”

Where is vars.bat or if you just post the lines in it, that would be fine?
Thanks.

16. Re: Buiilt 4.1 64 bit on WIndows failed

• Posted by Steady Jan 26, 2014
• 2081 views

Thanks for the prompt reply.
As I understand it, the call to a batch file ......vars.bat was an intention to add the path to your location for mingw32\bin and msys\bin.
I have never built from scratch, but I will have a go, or several gos and hopefully I will succeed.