This problem mysteriously disappeared. I have no idea why. It might have something to do with logging out and logging in again, but it wasn't the first time I tried that.
Prolog behaves as if it sends the compiled file to /dev/null. 192-168-1-112:expert barry$ uname -a Darwin 192-168-1-112.tpgi.com.au 12.4.0 Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64 configure was not used. The same behaviour occurs with any source file on my MacBook Air, but all is well on my iMac desktop. 192-168-1-112:expert barry$ /opt/local/bin/gprolog GNU Prolog 1.4.4 (64 bits) Compiled Apr 23 2013, 17:26:17 with /opt/local/bin/gcc-apple-4.2 By Daniel Diaz Copyright (C) 1999-2013 Daniel Diaz | ?- [database]. compiling /Users/barry/Dropbox/SA&S/expert/database.pro for byte code... /Users/barry/Dropbox/SA&S/expert/database.pro compiled, 70 lines read - 18597 bytes written, 30 ms (5 ms) yes | ?- listing. yes | ?- subject(A,B,C,D,E). uncaught exception: error(existence_error(procedure,subject/5),top_level/0) | ?- halt. Attempting to call any predicate in a compiled file fails. Barry Dwyer barry.dw...@me.com _______________________________________________ Bug-prolog mailing list Bug-prolog@gnu.org https://lists.gnu.org/mailman/listinfo/bug-prolog
