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

nodejs library build fails with missing symbol uv-fs-stat-cb-vector-props #96

Open
pmatos opened this issue Mar 1, 2023 · 3 comments
Open

Comments

@pmatos
Copy link
Contributor

pmatos commented Mar 1, 2023

I am trying to use the JS compiler inside hop. I compiled bigloo and hop just fine (modulo the PRs I added).

Compiling a JS file with hop complains about a missing nodejs.heap. This file seems to be generated by hop/nodejs, but not distributed with any binary package. Trying to run make inside this folder complains about missing symbol uv-fs-stat-cb-vector-props. Disabling libuv at configure time makes the process of building the nodejs library earlier on.

I did notice that this variable showed up in the very last commit and reverting the last commit for uv.scm allows nodejs.heap to be built.

I have also tried a couple of different libuv versions in case mine is too recent but didn't have much luck.

@bentxt
Copy link

bentxt commented Apr 24, 2023

I'm on macos and I have the same error

@manuel-serrano
Copy link
Owner

Hi everyone,

Sorry about that.

This error is a Bigloo backward compatibilty problem. During the last weeks
I have very significantly improved the performance of the libuv binding
and this needed some new functions to be implemented directly by the
Bigloo compiler. I have tried to protect these new optimization with
"cond-expand" code so that Hop can still be compiled with older Bigloo
versions but I have missed some places here and there. I have now fixed that
and it should be able to build Hop again with old Bigloo version. I have
pushed that new version of the github repo. Please let me know if you are
still facing problems.

Once again, all my apologizes for the inconvenience.

@bentxt
Copy link

bentxt commented May 22, 2023

Thanks for all your efforts
I tried to build it with a fresh checkout and while I no longer get this error I get a new one #101

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