Re: Compiling Euphoria 3+ for non-x86 targets
- Posted by "Mark Brown" <mabrown at ihug.com.au> Mar 24, 2007
- 520 views
Shawn Pringle wrote: > Unless I misunderstood you, you said that you lost the source of your > old port yet you still have the binary [snip] Hi Shawn. Sorry for the slow reply and thanks for the suggested work around. As it stands, I actually seem to have created a mostly working version of the 3.0.2 interpreter for my Zaurus. In the end I have had to translate the front-end on my Linux PC, copy the translated files to my Zaurus and then compile the interpreter from there. If I do it this way the seg-faults disappear in the resulting interpreter. If I then use that working interpreter to create a new set of translated front-end C files and recompile, the resulting interpreter seg-faults, just as it does if I use my 2.5 Zaurus compile to do the translation! It seems that my 2.5 and 3.0.2 Zaurus interpreters produce different translated front-end C code to the official interpreter on my Linux laptop. I assume that they should produce exactly the same output. I've only compared the Zaurus and PC translated files for size. Some of the files are exactly the same size, others slightly or very different. Both the Zaurus and PC translated code compiles fine though. I'm going to have to do a side by side comparison of the translator output, although I may not learn much... I'm reaching the limits of my skills pretty fast :). There is obviously more I need to do to create a reliable port. Mark