teyjus - Project Hosting on Google Code

Today 21 hours ago issue 43 (Unable to install Teyjus on Mac Os X Snow Leopard) reported by jja...@isc.cnrs.fr - What steps will reproduce the problem? 1. uncompress the Teyjus archive for Linux and Mac 2. omake all What is the expected output? What do you see instead? What I expect Smooth compiling ... What I get wheraIam$ sudo omake all * omake: reading OMakefiles --- Checking if ocamldep understands -modules... (yes) --- Checking for ocamlfind... (FAILED - no ocamlfind found) --- Checking for ocamlc.opt... (found /usr/local/bin/ocamlc.opt) --- Checking for ocamlopt.opt... (found /usr/local/bin/ocamlopt.opt) --- Checking whether ocamlc understands the "z" warnings... (yes) * omake: finished reading OMakefiles (0.23 sec) - build source/compiler errormsg.o + ocamlopt.opt -warn-error A -I . -I . -I ../disassembler -I ../simulator -I ../loader -c errormsg.ml /tmp/camlasm254160.s:187:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:187:cannot do signed 4 byte relocation /tmp/camlasm254160.s:196:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:196:cannot do signed 4 byte relocation /tmp/camlasm254160.s:241:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:241:cannot do signed 4 byte relocation /tmp/camlasm254160.s:246:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:246:cannot do signed 4 byte relocation /tmp/camlasm254160.s:251:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:251:cannot do signed 4 byte relocation /tmp/camlasm254160.s:254:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:254:cannot do signed 4 byte relocation /tmp/camlasm254160.s:272:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:272:cannot do signed 4 byte relocation /tmp/camlasm254160.s:276:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:276:cannot do signed 4 byte relocation /tmp/camlasm254160.s:281:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:281:cannot do signed 4 byte relocation /tmp/camlasm254160.s:285:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:285:cannot do signed 4 byte relocation /tmp/camlasm254160.s:291:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:291:cannot do signed 4 byte relocation /tmp/camlasm254160.s:294:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:294:cannot do signed 4 byte relocation /tmp/camlasm254160.s:312:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:312:cannot do signed 4 byte relocation /tmp/camlasm254160.s:320:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:320:cannot do signed 4 byte relocation /tmp/camlasm254160.s:323:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:323:cannot do signed 4 byte relocation /tmp/camlasm254160.s:342:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:342:cannot do signed 4 byte relocation /tmp/camlasm254160.s:347:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:347:cannot do signed 4 byte relocation /tmp/camlasm254160.s:350:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:350:cannot do signed 4 byte relocation /tmp/camlasm254160.s:357:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:357:cannot do signed 4 byte relocation /tmp/camlasm254160.s:359:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:359:cannot do signed 4 byte relocation /tmp/camlasm254160.s:360:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:360:cannot do signed 4 byte relocation /tmp/camlasm254160.s:364:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:364:cannot do signed 4 byte relocation /tmp/camlasm254160.s:366:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:366:cannot do signed 4 byte relocation /tmp/camlasm254160.s:367:suffix or operands invalid for `pop' /tmp/camlasm254160.s:384:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:384:cannot do signed 4 byte relocation /tmp/camlasm254160.s:388:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:388:cannot do signed 4 byte relocation /tmp/camlasm254160.s:392:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:392:cannot do signed 4 byte relocation /tmp/camlasm254160.s:396:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:396:cannot do signed 4 byte relocation /tmp/camlasm254160.s:400:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:400:cannot do signed 4 byte relocation /tmp/camlasm254160.s:404:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:404:cannot do signed 4 byte relocation /tmp/camlasm254160.s:406:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:406:cannot do signed 4 byte relocation /tmp/camlasm254160.s:408:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:408:cannot do signed 4 byte relocation /tmp/camlasm254160.s:410:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:410:cannot do signed 4 byte relocation /tmp/camlasm254160.s:412:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:412:cannot do signed 4 byte relocation /tmp/camlasm254160.s:414:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:414:cannot do signed 4 byte relocation /tmp/camlasm254160.s:416:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:416:cannot do signed 4 byte relocation /tmp/camlasm254160.s:418:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:418:cannot do signed 4 byte relocation /tmp/camlasm254160.s:420:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:420:cannot do signed 4 byte relocation /tmp/camlasm254160.s:422:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:422:cannot do signed 4 byte relocation /tmp/camlasm254160.s:424:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:424:cannot do signed 4 byte relocation /tmp/camlasm254160.s:584:unknown section type: non_lazy_symbol_pointers /tmp/camlasm254160.s:584:Rest of line ignored. 1st junk character valued 32 ( ). File "errormsg.ml", line 1, characters 0-1: Error: Assembler error, input left in file /tmp/camlasm254160.s * omake: 52/595 targets are up to date * omake: failed (0.39 sec, 2/2 scans, 2/2 rules, 17/242 digests) * omake: targets were not rebuilt because of errors: source/compiler/errormsg.cmx depends on: source/compiler/errormsg.ml source/compiler/errormsg.o depends on: source/compiler/errormsg.ml What version of the product are you using? On what operating system? Last version OS : Mac Os X Snow Leopard Please provide any additional information below. A 32 vs. 64 bit conflict? Probably. But omake does not suggest any workaround What steps will reproduce the problem? 1. uncompress the Teyjus archive for Linux and Mac 2. omake all What is the expected output? What do you see instead? What I expect Smooth compiling ... What I get wheraIam$ sudo omake all * omake: reading OMakefiles --- Checking if ocamldep understands -modules... (yes) --- Checking for ocamlfind... (FAILED - no ocamlfind found) --- Checking for ocamlc.opt... (found /usr/local/bin/ocamlc.opt) --- Checking for ocamlopt.opt... (found /usr/local/bin/ocamlopt.opt) --- Checking whether ocamlc understands the "z" warnings... (yes) * omake: finished reading OMakefiles (0.23 sec) - build source/compiler errormsg.o + ocamlopt.opt -warn-error A -I . -I . -I ../disassembler -I ../simulator -I ../loader -c errormsg.ml /tmp/camlasm254160.s:187:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:187:cannot do signed 4 byte relocation /tmp/camlasm254160.s:196:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:196:cannot do signed 4 byte relocation /tmp/camlasm254160.s:241:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:241:cannot do signed 4 byte relocation /tmp/camlasm254160.s:246:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:246:cannot do signed 4 byte relocation /tmp/camlasm254160.s:251:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:251:cannot do signed 4 byte relocation /tmp/camlasm254160.s:254:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:254:cannot do signed 4 byte relocation /tmp/camlasm254160.s:272:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:272:cannot do signed 4 byte relocation /tmp/camlasm254160.s:276:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:276:cannot do signed 4 byte relocation /tmp/camlasm254160.s:281:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:281:cannot do signed 4 byte relocation /tmp/camlasm254160.s:285:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:285:cannot do signed 4 byte relocation /tmp/camlasm254160.s:291:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:291:cannot do signed 4 byte relocation /tmp/camlasm254160.s:294:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:294:cannot do signed 4 byte relocation /tmp/camlasm254160.s:312:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:312:cannot do signed 4 byte relocation /tmp/camlasm254160.s:320:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:320:cannot do signed 4 byte relocation /tmp/camlasm254160.s:323:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:323:cannot do signed 4 byte relocation /tmp/camlasm254160.s:342:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:342:cannot do signed 4 byte relocation /tmp/camlasm254160.s:347:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:347:cannot do signed 4 byte relocation /tmp/camlasm254160.s:350:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:350:cannot do signed 4 byte relocation /tmp/camlasm254160.s:357:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:357:cannot do signed 4 byte relocation /tmp/camlasm254160.s:359:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:359:cannot do signed 4 byte relocation /tmp/camlasm254160.s:360:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:360:cannot do signed 4 byte relocation /tmp/camlasm254160.s:364:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:364:cannot do signed 4 byte relocation /tmp/camlasm254160.s:366:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:366:cannot do signed 4 byte relocation /tmp/camlasm254160.s:367:suffix or operands invalid for `pop' /tmp/camlasm254160.s:384:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:384:cannot do signed 4 byte relocation /tmp/camlasm254160.s:388:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:388:cannot do signed 4 byte relocation /tmp/camlasm254160.s:392:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:392:cannot do signed 4 byte relocation /tmp/camlasm254160.s:396:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:396:cannot do signed 4 byte relocation /tmp/camlasm254160.s:400:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:400:cannot do signed 4 byte relocation /tmp/camlasm254160.s:404:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:404:cannot do signed 4 byte relocation /tmp/camlasm254160.s:406:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:406:cannot do signed 4 byte relocation /tmp/camlasm254160.s:408:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:408:cannot do signed 4 byte relocation /tmp/camlasm254160.s:410:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:410:cannot do signed 4 byte relocation /tmp/camlasm254160.s:412:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:412:cannot do signed 4 byte relocation /tmp/camlasm254160.s:414:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:414:cannot do signed 4 byte relocation /tmp/camlasm254160.s:416:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:416:cannot do signed 4 byte relocation /tmp/camlasm254160.s:418:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:418:cannot do signed 4 byte relocation /tmp/camlasm254160.s:420:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:420:cannot do signed 4 byte relocation /tmp/camlasm254160.s:422:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:422:cannot do signed 4 byte relocation /tmp/camlasm254160.s:424:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:424:cannot do signed 4 byte relocation /tmp/camlasm254160.s:584:unknown section type: non_lazy_symbol_pointers /tmp/camlasm254160.s:584:Rest of line ignored. 1st junk character valued 32 ( ). File "errormsg.ml", line 1, characters 0-1: Error: Assembler error, input left in file /tmp/camlasm254160.s * omake: 52/595 targets are up to date * omake: failed (0.39 sec, 2/2 scans, 2/2 rules, 17/242 digests) * omake: targets were not rebuilt because of errors: source/compiler/errormsg.cmx depends on: source/compiler/errormsg.ml source/compiler/errormsg.o depends on: source/compiler/errormsg.ml What version of the product are you using? On what operating system? Last version OS : Mac Os X Snow Leopard Please provide any additional information below. A 32 vs. 64 bit conflict? Probably. But omake does not suggest any workaround Last 30 days Dec 08, 2009 issue 42 (tjsim crashes when parsing incorrect goal) reported by dale.a.miller - I typed a lambda term (type, say, i -> i) as the goal. Instead of reporting an parsing / typing error, the system aborted. -Dale $ tjsim -v Teyjus version 2.0-b1 $ uname -a Linux alonzo 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:00:22 UTC 2009 i686 GNU/Linux $ tjsim Welcome to Teyjus Copyright (C) 2008 A. Gacek, S. Holte, G. Nadathur, X. Qi, Z. Snow Teyjus comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions. Please view the accompanying file COPYING for more information [toplevel] ?- (x\x). none(0,0) : Internal Error : Absyn.getTermAbstractionVar: invalid term Uncaught internal exception $ I typed a lambda term (type, say, i -> i) as the goal. Instead of reporting an parsing / typing error, the system aborted. -Dale $ tjsim -v Teyjus version 2.0-b1 $ uname -a Linux alonzo 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:00:22 UTC 2009 i686 GNU/Linux $ tjsim Welcome to Teyjus Copyright (C) 2008 A. Gacek, S. Holte, G. Nadathur, X. Qi, Z. Snow Teyjus comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions. Please view the accompanying file COPYING for more information [toplevel] ?- (x\x). none(0,0) : Internal Error : Absyn.getTermAbstractionVar: invalid term Uncaught internal exception $ Older Nov 18, 2009 TeyjusTokens (Tokens in Teyjus) Wiki page edited by andrew.gacek - Revision r981 We do not allow \ in the name of variables. This would conflict with our use of \ as a lambda. I have confirmed this in the implementation. Revision r981 We do not allow \ in the name of variables. This would conflict with our use of \ as a lambda. I have confirmed this in the implementation. Oct 21, 2009 issue 39 (Accum_sig and Use_sig in modules are broken.) commented on by zacharyrsnow - Fixed in r980. Fixed in r980. Oct 21, 2009 issue 38 (Extending redefinable predicates crashes the compiler.) Status changed by zacharyrsnow - Fixed in r980. Status: Fixed Fixed in r980. Status: Fixed Oct 21, 2009 issue 39 (Accum_sig and Use_sig in modules are broken.) changed by zacharyrsnow - This issue was closed by revision r980. Status: Fixed This issue was closed by revision r980. Status: Fixed Oct 21, 2009 r980 (Fixed issue 38 by changing pervasives so that they are initi...) committed by zacharyrsnow - Fixed issue 38 by changing pervasives so that they are initially 'nodefs'; this flag is of course reset when redefinable pervasives are redefined. Fixed issue 39 by adding use_sig and accum_sig to modules. The effect of these are essentially the same as the effect of use and accumulate, but the relevant modules are not linked in (the only effect is on the symbol table). Fixed issue 38 by changing pervasives so that they are initially 'nodefs'; this flag is of course reset when redefinable pervasives are redefined. Fixed issue 39 by adding use_sig and accum_sig to modules. The effect of these are essentially the same as the effect of use and accumulate, but the relevant modules are not linked in (the only effect is on the symbol table). Oct 18, 2009 issue 41 (Hidden names can escape when there are disagreement pairs) changed by qixx0019 - The fix has be checked in as r979. The problem turns out to be caused by a silly bug in the implementation of get_{m/p}_structure: in the case that the incoming term is directly a free variable (no head normalization is needed), no checking was made on its and the structure head's universe counts. The fix is to add the check and to fail when the universe count of the structure head is greater than that of the free variable. Status: Fixed Owner: qixx0019 Cc: andrew.gacek gopalan.nadathur The fix has be checked in as r979. The problem turns out to be caused by a silly bug in the implementation of get_{m/p}_structure: in the case that the incoming term is directly a free variable (no head normalization is needed), no checking was made on its and the structure head's universe counts. The fix is to add the check and to fail when the universe count of the structure head is greater than that of the free variable. Status: Fixed Owner: qixx0019 Cc: andrew.gacek gopalan.nadathur Oct 18, 2009 r979 (Fix issue 41. The problem turns out to be caused by a silly...) committed by qixx0019 - Fix issue 41 . The problem turns out to be caused by a silly bug in the implementation of get_{m/p}_structure: in the case that the incoming term is directly a free variable (no head normalization is needed), no checking was made on its and the structure head's universe counts. The fix is to add the check and to fail when the universe count of the structure head is greater than that of the free variable. Fix issue 41 . The problem turns out to be caused by a silly bug in the implementation of get_{m/p}_structure: in the case that the incoming term is directly a free variable (no head normalization is needed), no checking was made on its and the structure head's universe counts. The fix is to add the check and to fail when the universe count of the structure head is greater than that of the free variable. Oct 12, 2009 r978 (Updated svn:ignore for tjparse) committed by andrew.gacek - Updated svn:ignore for tjparse Updated svn:ignore for tjparse Oct 06, 2009 r977 (Added an executable 'tjparse' which reads a module, syntacti...) committed by zacharyrsnow - Added an executable 'tjparse' which reads a module, syntactically and semantically analyzes it, and then pretty-prints the module in such a way as the pretty-printed output is a drop-in replacement for the read module (works but will be improved). Also updated the Visual Studio solution, OMakefiles and installer script to know about tjparse. In the process type skeleton pretty-printing was changed, hence the huge changeset for tests; these are all changes due to skeleton printing, and nothing else. Standardized the usage information for all executables and updated the relevant READMEs. Added an executable 'tjparse' which reads a module, syntactically and semantically analyzes it, and then pretty-prints the module in such a way as the pretty-printed output is a drop-in replacement for the read module (works but will be improved). Also updated the Visual Studio solution, OMakefiles and installer script to know about tjparse. In the process type skeleton pretty-printing was changed, hence the huge changeset for tests; these are all changes due to skeleton printing, and nothing else. Standardized the usage information for all executables and updated the relevant READMEs. Oct 01, 2009 r976 (New scratch test for extending builtins.) committed by zacharyrsnow - New scratch test for extending builtins. New scratch test for extending builtins. Sep 29, 2009 r975 (Fixed --quiet flag so it does something; some tiny cleanup.) committed by zacharyrsnow - Fixed --quiet flag so it does something; some tiny cleanup. Fixed --quiet flag so it does something; some tiny cleanup. Sep 28, 2009 r974 (Deleted obsolete Visual Studio file.) committed by zacharyrsnow - Deleted obsolete Visual Studio file. Deleted obsolete Visual Studio file. Sep 22, 2009 r973 (Fixed mixed tabs/spaces.) committed by zacharyrsnow - Fixed mixed tabs/spaces. Fixed mixed tabs/spaces. Sep 18, 2009 r972 (Created issue directories for bugs in the renaming branch I...) committed by andrew.gacek - Created issue directories for bugs in the renaming branch I have created the directories issue1 and issue2 which contain examples of bugs in the renaming branch. If you run 'tjcc root' in an issue directory (or more generally run 'make') you should see the erroneous behavior. I have also documented the errors in the sig/mod files. Putting bugs into these types of toplevel directories may not be the best practice, but it should be okay for exchanging this type of information, particularly on a branch. We should find a way to migrate such things into automated test cases. Created issue directories for bugs in the renaming branch I have created the directories issue1 and issue2 which contain examples of bugs in the renaming branch. If you run 'tjcc root' in an issue directory (or more generally run 'make') you should see the erroneous behavior. I have also documented the errors in the sig/mod files. Putting bugs into these types of toplevel directories may not be the best practice, but it should be okay for exchanging this type of information, particularly on a branch. We should find a way to migrate such things into automated test cases. Sep 18, 2009 issue 41 (Hidden names can escape when there are disagreement pairs) reported by andrew.gacek - Consider the following development. eval.sig: sig eval. kind tm type. type abs (tm -> tm) -> tm. type eval tm -> tm -> o. eval.mod: module eval. type app tm -> tm -> tm. eval (abs R) (abs R). eval (app M N) V :- eval M (abs R), eval (R N) V. Now consider the following interaction. [eval] ?- eval E (abs x\ x). The answer substitution: E = abs (W1\ W1) More solutions (y/n)? y The answer substitution: E = <lc-0-1> (abs _T1) _T2 The remaining disagreement pairs list: <_T1 _T2, abs (W1\ W1)> Notice that the hidden name 'app' is escaping in the form of <lc-0-1>. I have only been able to recreate this for solutions which result in disagreement pairs. Yet, no matter how this disagreement pair is solved, <lc-0-1> would leak out. I can understand if perhaps such variables may need to occur in disagreement pairs because the solutions to such pairs might end up projecting that variable away. However, they should never be allowed in solutions. Consider the following development. eval.sig: sig eval. kind tm type. type abs (tm -> tm) -> tm. type eval tm -> tm -> o. eval.mod: module eval. type app tm -> tm -> tm. eval (abs R) (abs R). eval (app M N) V :- eval M (abs R), eval (R N) V. Now consider the following interaction. [eval] ?- eval E (abs x\ x). The answer substitution: E = abs (W1\ W1) More solutions (y/n)? y The answer substitution: E = <lc-0-1> (abs _T1) _T2 The remaining disagreement pairs list: <_T1 _T2, abs (W1\ W1)> Notice that the hidden name 'app' is escaping in the form of <lc-0-1>. I have only been able to recreate this for solutions which result in disagreement pairs. Yet, no matter how this disagreement pair is solved, <lc-0-1> would leak out. I can understand if perhaps such variables may need to occur in disagreement pairs because the solutions to such pairs might end up projecting that variable away. However, they should never be allowed in solutions. Sep 17, 2009 issue 40 (Recursive accumulates should result in an error) reported by andrew.gacek - Right now a recursive accum_sig will cause the compiler to loop (and usually run out of memory resulting in no error message). Instead, it should result in an error right away. A recursive accumulate does not seem to do anything, but should also result in an error. Any other commands that might accidentally be applied recursively should result in the same error. Note that all of this includes any recursive (eg, if A accum_sigs B accum_sigs C accum_sigs A). Right now a recursive accum_sig will cause the compiler to loop (and usually run out of memory resulting in no error message). Instead, it should result in an error right away. A recursive accumulate does not seem to do anything, but should also result in an error. Any other commands that might accidentally be applied recursively should result in the same error. Note that all of this includes any recursive (eg, if A accum_sigs B accum_sigs C accum_sigs A). Sep 17, 2009 issue 39 (Accum_sig and Use_sig in modules are broken.) reported by zacharyrsnow - Steps: 1. Use either keyword in a module. 2. Compile. 3. It's as if the directives weren't even there. See translate.ml; the used and accumulated signatures in a module are dropped. Steps: 1. Use either keyword in a module. 2. Compile. 3. It's as if the directives weren't even there. See translate.ml; the used and accumulated signatures in a module are dropped. Sep 17, 2009 issue 38 (Extending redefinable predicates crashes the compiler.) Labels changed by zacharyrsnow - Labels: Priority-Critical Labels: Priority-Critical Sep 17, 2009 issue 38 (Extending redefinable predicates crashes the compiler.) reported by zacharyrsnow - Steps: 1. Extend (but do not redefine) a redefinable predicate (like open_in). 2. Compile. 3. Watch it crash. I'm not sure that this should even be allowed; I think that pervasive predicates should be 'useonly' unless they are redefined. Steps: 1. Extend (but do not redefine) a redefinable predicate (like open_in). 2. Compile. 3. Watch it crash. I'm not sure that this should even be allowed; I think that pervasive predicates should be 'useonly' unless they are redefined. Sep 17, 2009 r971 (Added file and line info to "non-injective renaming" error m...) committed by andrew.gacek - Added file and line info to "non-injective renaming" error message Added file and line info to "non-injective renaming" error message Sep 17, 2009 r970 (A little bit of code cleanup) committed by andrew.gacek - A little bit of code cleanup A little bit of code cleanup Sep 16, 2009 ModSyntaxRenaming (Syntax of Modules with the additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r969 Edited wiki page through web user interface. Revision r969 Edited wiki page through web user interface. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r968 Edited wiki page through web user interface. Revision r968 Edited wiki page through web user interface. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r967 Edited wiki page through web user interface. Revision r967 Edited wiki page through web user interface. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r966 Edited wiki page through web user interface. Revision r966 Edited wiki page through web user interface. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r965 Edited wiki page through web user interface. Revision r965 Edited wiki page through web user interface. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r964 Edited wiki page through web user interface. Revision r964 Edited wiki page through web user interface. Sep 16, 2009 ModSyntaxRenaming (Syntax of Modules with the additional renaming syntax) Wiki page edited by andrew.gacek - Revision r963 Changed the formatting of code which appears in running text. We should use `...` when formatting such code. Revision r963 Changed the formatting of code which appears in running text. We should use `...` when formatting such code. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r962 Edited wiki page through web user interface. Revision r962 Edited wiki page through web user interface. Sep 16, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r961 Edited wiki page through web user interface. Revision r961 Edited wiki page through web user interface. Sep 16, 2009 ModSyntaxRenaming (Syntax of Modules with the additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r960 Edited wiki page through web user interface. Revision r960 Edited wiki page through web user interface. Sep 16, 2009 ModSyntaxRenaming (Syntax of Modules with the additional renaming syntax) Wiki page edited by gopalan.nadathur - Revision r959 Edited wiki page through web user interface. Revision r959 Edited wiki page through web user interface. Aug 30, 2009 r958 (Allowing kinds and consts to be hidden properly in accumulat...) committed by microdan - Allowing kinds and consts to be hidden properly in accumulate statements Allowing kinds and consts to be hidden properly in accumulate statements Aug 26, 2009 LambdaProlog (A description of the Lambda Prolog language) Wiki page edited by andrew.gacek - Revision r957 Added web links to higher-order logic programming paper Revision r957 Added web links to higher-order logic programming paper Aug 15, 2009 r956 (Fixing typos) committed by microdan - Fixing typos Fixing typos Aug 13, 2009 r955 (fixing bug in renaming. only remaining issue should be linke...) committed by microdan - fixing bug in renaming. only remaining issue should be linker fixing bug in renaming. only remaining issue should be linker Aug 12, 2009 r954 (First stab at allowing renamings in accumulate, accum_sig an...) committed by microdan - First stab at allowing renamings in accumulate, accum_sig and use_sig First stab at allowing renamings in accumulate, accum_sig and use_sig Aug 06, 2009 ModSyntaxRenaming (Syntax of Modules with the additional renaming syntax) Wiki page edited by microdan - Revision r953 Edited wiki page through web user interface. Revision r953 Edited wiki page through web user interface. Aug 06, 2009 SigSyntaxRenaming (Syntax of Signatures with additional renaming syntax) Wiki page added by microdan - Revision r952 Created wiki page through web user interface. Revision r952 Created wiki page through web user interface. Aug 06, 2009 ModSyntaxRenaming (Syntax of Modules with the additional renaming syntax) Wiki page added by microdan - Revision r951 Created wiki page through web user interface. Revision r951 Created wiki page through web user interface. Jun 13, 2009 r950 (Removed unused variables in lexer. Removed redundant error m...) committed by andrew.gacek - Removed unused variables in lexer. Removed redundant error message in parser. Removed unused variables in lexer. Removed redundant error message in parser. Jun 13, 2009 r949 (Fixing small bug with parser, and making simulator exit grac...) committed by microdan - Fixing small bug with parser, and making simulator exit gracefully on EOF Fixing small bug with parser, and making simulator exit gracefully on EOF May 07, 2009 AbstractMachine (The Lambda Prolog Abstract Machine) Wiki page edited by gopalan.nadathur Mar 30, 2009 r947 (Set svn:ignore for Issue24) committed by andrew.gacek - Set svn:ignore for Issue24 Set svn:ignore for Issue24 Mar 25, 2009 r946 (Updated the Teyjus emacs mode so that syntax highlighting pr...) committed by andrew.gacek - Updated the Teyjus emacs mode so that syntax highlighting properly treats nested /* ... / comments. Updated the Teyjus emacs mode so that syntax highlighting properly treats nested / ... */ comments. Nov 16, 2008 teyjus-source-2.0-b2.tar.gz (Source tarball) file uploaded by andrew.gacek - Labels: Featured Type-Source OpSys-All Labels: Featured Type-Source OpSys-All Nov 16, 2008 teyjus-installer-2.0-b2.exe (Windows installer) file uploaded by andrew.gacek - Labels: Featured Type-Installer OpSys-Windows Labels: Featured Type-Installer OpSys-Windows Nov 16, 2008 r945 (Added a distclean target which is used by the windows instal...) committed by andrew.gacek - Added a distclean target which is used by the windows installer Added a distclean target which is used by the windows installer

issue 43 (Unable to install Teyjus on Mac Os X Snow Leopard) reported by jja...@isc.cnrs.fr - What steps will reproduce the problem? 1. uncompress the Teyjus archive for Linux and Mac 2. omake all What is the expected output? What do you see instead? What I expect Smooth compiling ... What I get wheraIam$ sudo omake all *** omake: reading OMakefiles --- Checking if ocamldep understands -modules... (yes) --- Checking for ocamlfind... (FAILED - no ocamlfind found) --- Checking for ocamlc.opt... (found /usr/local/bin/ocamlc.opt) --- Checking for ocamlopt.opt... (found /usr/local/bin/ocamlopt.opt) --- Checking whether ocamlc understands the "z" warnings... (yes) *** omake: finished reading OMakefiles (0.23 sec) - build source/compiler errormsg.o + ocamlopt.opt -warn-error A -I . -I . -I ../disassembler -I ../simulator -I ../loader -c errormsg.ml /tmp/camlasm254160.s:187:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:187:cannot do signed 4 byte relocation /tmp/camlasm254160.s:196:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:196:cannot do signed 4 byte relocation /tmp/camlasm254160.s:241:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:241:cannot do signed 4 byte relocation /tmp/camlasm254160.s:246:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:246:cannot do signed 4 byte relocation /tmp/camlasm254160.s:251:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:251:cannot do signed 4 byte relocation /tmp/camlasm254160.s:254:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:254:cannot do signed 4 byte relocation /tmp/camlasm254160.s:272:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:272:cannot do signed 4 byte relocation /tmp/camlasm254160.s:276:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:276:cannot do signed 4 byte relocation /tmp/camlasm254160.s:281:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:281:cannot do signed 4 byte relocation /tmp/camlasm254160.s:285:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:285:cannot do signed 4 byte relocation /tmp/camlasm254160.s:291:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:291:cannot do signed 4 byte relocation /tmp/camlasm254160.s:294:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:294:cannot do signed 4 byte relocation /tmp/camlasm254160.s:312:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:312:cannot do signed 4 byte relocation /tmp/camlasm254160.s:320:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:320:cannot do signed 4 byte relocation /tmp/camlasm254160.s:323:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:323:cannot do signed 4 byte relocation /tmp/camlasm254160.s:342:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:342:cannot do signed 4 byte relocation /tmp/camlasm254160.s:347:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:347:cannot do signed 4 byte relocation /tmp/camlasm254160.s:350:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:350:cannot do signed 4 byte relocation /tmp/camlasm254160.s:357:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:357:cannot do signed 4 byte relocation /tmp/camlasm254160.s:359:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:359:cannot do signed 4 byte relocation /tmp/camlasm254160.s:360:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:360:cannot do signed 4 byte relocation /tmp/camlasm254160.s:364:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:364:cannot do signed 4 byte relocation /tmp/camlasm254160.s:366:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:366:cannot do signed 4 byte relocation /tmp/camlasm254160.s:367:suffix or operands invalid for `pop' /tmp/camlasm254160.s:384:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:384:cannot do signed 4 byte relocation /tmp/camlasm254160.s:388:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:388:cannot do signed 4 byte relocation /tmp/camlasm254160.s:392:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:392:cannot do signed 4 byte relocation /tmp/camlasm254160.s:396:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:396:cannot do signed 4 byte relocation /tmp/camlasm254160.s:400:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:400:cannot do signed 4 byte relocation /tmp/camlasm254160.s:404:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:404:cannot do signed 4 byte relocation /tmp/camlasm254160.s:406:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:406:cannot do signed 4 byte relocation /tmp/camlasm254160.s:408:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:408:cannot do signed 4 byte relocation /tmp/camlasm254160.s:410:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:410:cannot do signed 4 byte relocation /tmp/camlasm254160.s:412:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:412:cannot do signed 4 byte relocation /tmp/camlasm254160.s:414:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:414:cannot do signed 4 byte relocation /tmp/camlasm254160.s:416:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:416:cannot do signed 4 byte relocation /tmp/camlasm254160.s:418:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:418:cannot do signed 4 byte relocation /tmp/camlasm254160.s:420:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:420:cannot do signed 4 byte relocation /tmp/camlasm254160.s:422:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:422:cannot do signed 4 byte relocation /tmp/camlasm254160.s:424:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:424:cannot do signed 4 byte relocation /tmp/camlasm254160.s:584:unknown section type: non_lazy_symbol_pointers /tmp/camlasm254160.s:584:Rest of line ignored. 1st junk character valued 32 ( ). File "errormsg.ml", line 1, characters 0-1: Error: Assembler error, input left in file /tmp/camlasm254160.s *** omake: 52/595 targets are up to date *** omake: failed (0.39 sec, 2/2 scans, 2/2 rules, 17/242 digests) *** omake: targets were not rebuilt because of errors: source/compiler/errormsg.cmx depends on: source/compiler/errormsg.ml source/compiler/errormsg.o depends on: source/compiler/errormsg.ml What version of the product are you using? On what operating system? Last version OS : Mac Os X Snow Leopard Please provide any additional information below. A 32 vs. 64 bit conflict? Probably. But omake does not suggest any workaround

What steps will reproduce the problem? 1. uncompress the Teyjus archive for Linux and Mac 2. omake all What is the expected output? What do you see instead? What I expect Smooth compiling ... What I get wheraIam$ sudo omake all *** omake: reading OMakefiles --- Checking if ocamldep understands -modules... (yes) --- Checking for ocamlfind... (FAILED - no ocamlfind found) --- Checking for ocamlc.opt... (found /usr/local/bin/ocamlc.opt) --- Checking for ocamlopt.opt... (found /usr/local/bin/ocamlopt.opt) --- Checking whether ocamlc understands the "z" warnings... (yes) *** omake: finished reading OMakefiles (0.23 sec) - build source/compiler errormsg.o + ocamlopt.opt -warn-error A -I . -I . -I ../disassembler -I ../simulator -I ../loader -c errormsg.ml /tmp/camlasm254160.s:187:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:187:cannot do signed 4 byte relocation /tmp/camlasm254160.s:196:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:196:cannot do signed 4 byte relocation /tmp/camlasm254160.s:241:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:241:cannot do signed 4 byte relocation /tmp/camlasm254160.s:246:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:246:cannot do signed 4 byte relocation /tmp/camlasm254160.s:251:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:251:cannot do signed 4 byte relocation /tmp/camlasm254160.s:254:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:254:cannot do signed 4 byte relocation /tmp/camlasm254160.s:272:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:272:cannot do signed 4 byte relocation /tmp/camlasm254160.s:276:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:276:cannot do signed 4 byte relocation /tmp/camlasm254160.s:281:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:281:cannot do signed 4 byte relocation /tmp/camlasm254160.s:285:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:285:cannot do signed 4 byte relocation /tmp/camlasm254160.s:291:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:291:cannot do signed 4 byte relocation /tmp/camlasm254160.s:294:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:294:cannot do signed 4 byte relocation /tmp/camlasm254160.s:312:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:312:cannot do signed 4 byte relocation /tmp/camlasm254160.s:320:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:320:cannot do signed 4 byte relocation /tmp/camlasm254160.s:323:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:323:cannot do signed 4 byte relocation /tmp/camlasm254160.s:342:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:342:cannot do signed 4 byte relocation /tmp/camlasm254160.s:347:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:347:cannot do signed 4 byte relocation /tmp/camlasm254160.s:350:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:350:cannot do signed 4 byte relocation /tmp/camlasm254160.s:357:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:357:cannot do signed 4 byte relocation /tmp/camlasm254160.s:359:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:359:cannot do signed 4 byte relocation /tmp/camlasm254160.s:360:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:360:cannot do signed 4 byte relocation /tmp/camlasm254160.s:364:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:364:cannot do signed 4 byte relocation /tmp/camlasm254160.s:366:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:366:cannot do signed 4 byte relocation /tmp/camlasm254160.s:367:suffix or operands invalid for `pop' /tmp/camlasm254160.s:384:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:384:cannot do signed 4 byte relocation /tmp/camlasm254160.s:388:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:388:cannot do signed 4 byte relocation /tmp/camlasm254160.s:392:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:392:cannot do signed 4 byte relocation /tmp/camlasm254160.s:396:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:396:cannot do signed 4 byte relocation /tmp/camlasm254160.s:400:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:400:cannot do signed 4 byte relocation /tmp/camlasm254160.s:404:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:404:cannot do signed 4 byte relocation /tmp/camlasm254160.s:406:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:406:cannot do signed 4 byte relocation /tmp/camlasm254160.s:408:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:408:cannot do signed 4 byte relocation /tmp/camlasm254160.s:410:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:410:cannot do signed 4 byte relocation /tmp/camlasm254160.s:412:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:412:cannot do signed 4 byte relocation /tmp/camlasm254160.s:414:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:414:cannot do signed 4 byte relocation /tmp/camlasm254160.s:416:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:416:cannot do signed 4 byte relocation /tmp/camlasm254160.s:418:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:418:cannot do signed 4 byte relocation /tmp/camlasm254160.s:420:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:420:cannot do signed 4 byte relocation /tmp/camlasm254160.s:422:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:422:cannot do signed 4 byte relocation /tmp/camlasm254160.s:424:32-bit absolute addressing is not supported for x86-64 /tmp/camlasm254160.s:424:cannot do signed 4 byte relocation /tmp/camlasm254160.s:584:unknown section type: non_lazy_symbol_pointers /tmp/camlasm254160.s:584:Rest of line ignored. 1st junk character valued 32 ( ). File "errormsg.ml", line 1, characters 0-1: Error: Assembler error, input left in file /tmp/camlasm254160.s *** omake: 52/595 targets are up to date *** omake: failed (0.39 sec, 2/2 scans, 2/2 rules, 17/242 digests) *** omake: targets were not rebuilt because of errors: source/compiler/errormsg.cmx depends on: source/compiler/errormsg.ml source/compiler/errormsg.o depends on: source/compiler/errormsg.ml What version of the product are you using? On what operating system? Last version OS : Mac Os X Snow Leopard Please provide any additional information below. A 32 vs. 64 bit conflict? Probably. But omake does not suggest any workaround

Today

Last 30 days

Older