1. euc question
- Posted by irv Nov 17, 2022
- 1384 views
-- version.ex include euphoria/info.e include std/console.e display(version_string())
irv@irv-desktop:~$ eui Euphoria Interpreter v4.2.0 development 64-bit Linux, Using System Memory Revision Date: 2022-07-03 04:24:05 Id: 29ec7a3b83a082a0b62ddb15f2dabeb4c1c52baf irv@irv-desktop:~$ euc Euphoria to C Translator v4.2.0 development 64-bit Linux, Using System Memory Revision Date: 2022-07-03 04:24:05 Id: 29ec7a3b83a082a0b62ddb15f2dabeb4c1c52baf
version.ex interpreted:
irv@irv-desktop:~$ eui version 4.2.0 development (-1:29ec7a3b83a0, 2022-07-03 04:24:05)
version.ex compiled:
irv@irv-desktop:~$ ./version 4.1.0 development (5861:57179171dbed, 2015-02-02 14:18:53)
?
2. Re: euc question
- Posted by ghaberek (admin) Nov 17, 2022
- 1388 views
The routines in euphoria/info.e get their information from the backend via machine_func(M_EU_INFO). When using the interpreter, backend functions are inside the interpreter itself. But when using the translator, backend functions are in the static library.
This tells me that you most likely have built a new translator but are still referencing an old static library. This is typically the case when you haven't fully "installed" what you've built or are not telling the new translator to use the new library in the build directory.
Did you use cp or make install to copy the binaries from the build directory to a system directory like /usr/local/euphoria/bin? If so, is the new eu.a or eudbg.a static library there as well? And is eu.cfg present and correct?
-Greg