Re: Translator problem?

new topic     » goto parent     » topic index » view thread      » older message » newer message
jeremy said...
LarryMiller said...

I tried the translator in svn 2015 (binaries from eubins) with a large application of mine. The translator produces many .c files. Everything went well until the link phase when the following error occured:

Error! E2028: init_literal0_ is an undefined reference file init-.obj(D:\Euphoria\EU32Lib\EuEditor\init-.c): undefined symbol init_literal0_

init_literal0_ is in init-.obj but not in init-.c.

This has also occured with a number of earlier versions. It worked with Alpha 2.

The application runs well when interpreted and it binds successfully. The translator works without problem with the Euphoria win32 demos.

Is this a bug in the translator or possibly in my application? I will report it on bugtracker if it is thought to be a bug.

I discovered this morning and committed a fix about 15 minutes ago. For me, init_literal0 was in init-0.c which was being generated but not included in the build files/compilation process. On larger projects init-.c is split into multiple files because some compilers/platforms will choke on large .c files. That is why it was not detected on the smaller examples/demos.

Please svn up (or get a later eubin and please let me know if that corrects your problem.

Jeremy

Jeremy

Updated to svn 2019 binaries and tried again. Still produces the same error.

The init-.c file is now split into two. init-.c 579,157 bytes init-0.c 77,159 bytes

Neither contains the symbol init_literal0_

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu