Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eye.pvm: incompatible VM-signature #104

Open
tpluscode opened this issue Feb 13, 2024 · 5 comments
Open

eye.pvm: incompatible VM-signature #104

tpluscode opened this issue Feb 13, 2024 · 5 comments

Comments

@tpluscode
Copy link

I installed eye from the install.sh script and I cannot run it

$> eye 
[FATAL ERROR: at Tue Feb 13 12:35:29 2024
        /usr/local/lib/eye.pvm: incompatible VM-signature (file: 0x9fa44fc5; Prolog: 0x408bfff4)]
/usr/local/bin/eye: line 2: 48350 Abort trap: 6           swipl -x /usr/local/lib/eye.pvm -- "$@"
version
eye 9.7.12
swipl SWI-Prolog version 9.2.0 for x86_64-darwin (installed with homebrew)
macOS Sonoma 14.2.1
@tpluscode
Copy link
Author

Earlier I had the same problem when I tried using eye from docker when I compiled rules to a PVM. eye -x worked fine but the swipl itself inside the container complained about the signature

@jeswr
Copy link
Member

jeswr commented Feb 13, 2024

@tpluscode Not a solution to your issue - but https://github.com/eyereasoner/eye-js and the PVM generator https://github.com/SWI-Prolog/npm-swipl-wasm?tab=readme-ov-file#generating-an-image might let you work around it for now by doing things is Webassebly.

@tpluscode
Copy link
Author

@josd do you have an idea?

I'm not on swipl 9.2.9, macOS 15.2 and eye 11.4.7 still produces the same error 🤔

@josd
Copy link
Collaborator

josd commented Jan 22, 2025

It should be gone after you run https://github.com/eyereasoner/eye/blob/master/INSTALL#L15-L17
If not I don't know :-)

@tpluscode
Copy link
Author

The error means that the eye.pvm was compiled with swipl not matching the one installed on my machine?

Hm, it appears that the script does not do what the readme says. I'm confused as to what eye actually ended up in my PATH but installer put the binaries in /opt, which is not in PATH.

Adding --profile explicitly was necessary and now it works just fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants