#5700 closed defect (worksforme)
Failed to compile all functions in package SimCodeUtil. Error: Type mismatch.
Reported by: | Owned by: | Martin Sjölund | |
---|---|---|---|
Priority: | high | Milestone: | 1.14.0 |
Component: | Build Environment | Version: | v1.13.2 |
Keywords: | omc SimCodeUtil.mo SimCode | Cc: |
Description
Dear all,
I am unable to compile OMC. I get this message:
[/tmp/openmodelica-1.13.2/OMCompiler/Compiler/SimCode/SimCodeUtil.mo:12998:3-12998:60:writable] Error: Type mismatch in assignment in f2 := function Expression.traverseSubexpressions(f1) of .SimCodeUtil.getResources.Func<function>(DAE.Exp $in_e, AvlSetString.Tree $in_tree) => (DAE.Exp e, AvlSetString.Tree tree) := .Expression.traverseSubexpressions<function>(DAE.Exp $in_e, polymorphic<Type_a> $in_arg) => (DAE.Exp e, AvlSetString.Tree arg) [/tmp/openmodelica-1.13.2/OMCompiler/Compiler/SimCode/SimCodeUtil.mo:12998:3-12998:60:writable] Error: Type mismatch in pattern f2 expression type: .Expression.traverseSubexpressions<function>(DAE.Exp $in_e, polymorphic<Type_a> $in_arg) => (DAE.Exp e, AvlSetString.Tree arg) pattern type: .SimCodeUtil.getResources.Func<function>(DAE.Exp $in_e, AvlSetString.Tree $in_tree) => (DAE.Exp e, AvlSetString.Tree tree) [/tmp/openmodelica-1.13.2/OMCompiler/Compiler/SimCode/SimCodeUtil.mo:32:1-13068:16:writable] Error: Failed to compile all functions in package SimCodeUtil.
I am currently using code from openmodelica-1.13.2.r0.gcd9628b7a v1.13.2, and Submodule path 'OMCompiler' that I checked out is: '15ab15257673984eb4a273eaa17186cfb321ad73'
I see that master version of SimCodeUtil.mo doesn't change the code reported above.
Any hints?
Thank you,
VM
Change History (3)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
You probably need to ./configure --without-omc
if you had a different omc installed which wants a slightly different syntax.
comment:3 by , 5 years ago
Milestone: | Future → 1.14.0 |
---|
Note:
See TracTickets
for help on using tickets.
1.13.2 is now quite old and will be replaced soon by 1.14.0, which is currently in beta testing phase. 1.14.0 has a lot of bugfixes, so this problem may be solved already.
I would suggest you to retry with 1.14.0 (you can get it from the maintenance/v1.14 branch) and see if it works.