© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
OK. You are suggesting to apply the code changes in comment #9 to my source tree and compile again with 16.1.3. Did I understood correctly?
From comment #7, the way that I was trying to reason the error is that the ECL compiler incorrectly evaluated one of the arguments to the mod macro (function?) which results in the error printed in the logs. My question was if there is a way to determine which of the macros ECL failed on. Does the call to mod fails with that error when called with a zero on one of the arguments? Again, is this a valid reasoning or is this a case where the compiler bug occurred in a previous step is manifesting on this file? Thanks.