[Xsb-development] Interprolog troubles under Windows with the current CVS version of XSB

[<ki...@cs...>]

Report from the trenches regarding XSB/Interprolog on Windows (bad) and Linux (better)

Yesterday I claimed that XSB doesn't link with interprolog under native
windows -- that wasn't true. Apparently I had troubles with a network drive.

BUT, interprolog DOESN'T work with the current CVS version of XSB on
Windows.  It DOES work with XSB 2.7.1, however, so it is definitely a
current XSB problem.  I tried both with the latest release of Interprolog
and the one before that.

When I try Subprocess engine

    runXSBSPlistener.bat 

then it just hangs.
If I try the Native engine,

    runNativeListener.bat

I get a backtrace:

Cannot find the file/module C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\IP_14733
Exception in thread "main" com.declarativa.interprolog.util.IPException: Could not initialize XSB:com.declarativa.interprolog.util.IPException: Problem consulting from package archive:C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\IP_14733\xsb\interprolog.xwam
        at com.xsb.interprolog.AbstractNativeEngine.setupPrologSide(AbstractNati
veEngine.java)
        at com.xsb.interprolog.NativeEngine.<init>(NativeEngine.java)
        at com.xsb.interprolog.NativeEngine.<init>(NativeEngine.java)
        at com.xsb.interprolog.NativeEngineWindow.main(NativeEngineWindow.java)


The Linux situation:
    Under Linux, things are better. XSB 2.7.1 plain works.

    The Subprocess engine works with the latest XSB as well.
    But XSB can't be compiled for Native engine out of the box:

	makexsb dynmodule

    breaks because evansbj (Barry?) added the following in emuMakefile.in:

        -framework JavaVM -lSystem

    and now gcc/loader complain:

    	gcc: JavaVM: No such file or directory
	/usr/bin/ld: cannot find -lSystem


    But when I got rid of these nasty things then Interprolog worked with
    the latest XSB as well (under Linux).

    Barry, what are these supposed to do?



	--michael