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

symbol lookup error on nVidia #65

Closed
bryanlarsen opened this issue May 27, 2016 · 14 comments
Closed

symbol lookup error on nVidia #65

bryanlarsen opened this issue May 27, 2016 · 14 comments
Labels

Comments

@bryanlarsen
Copy link

node-gl was working fine for me inside Vagrant, then I tried speeding it up by using it on a machine with a real X server on an nVidia card and I got this error:

node: symbol lookup error: .../node_modules/gl/build/Release/webgl.node: undefined symbol: _Z15XextFindDisplayP15_XExtensionInfoP9_XDisplay

I fixed the error by recompiling everything and manually copying webgl.node into my installation.

@mikolalysenko
Copy link
Member

Seems like a problem with the prebuilt binaries linking statically against some X server configuration. Maybe the right solution would be to have the prebuild check if the module fails to load and in such an event rebuild the module from source.

@ralphtheninja do you know if there is a way to configure prebuild to do something like this?

@RaduMilici
Copy link

Hello! I think I'm having the exact same problem with headless-gl, but I'm a bit of a beginner and I'm not quite sure I understand you fix.

Can you please detail a bit what you did to make it work, I would appreciate it greatly. Thank you for reading. :)

@NHQ
Copy link

NHQ commented Sep 5, 2016

me too, details plz

@ralphtheninja
Copy link

@mikolalysenko Might be hard to check this, since it might load on the machine building the binaries but not on another machine.

You could use https://github.com/juliangruber/require-rebuild to have it be rebuilt on the target machine if the require fails

@NHQ
Copy link

NHQ commented Sep 6, 2016

require-rebuild didn't work for me, but it's a pretty rad hack!

On Mon, Sep 5, 2016 at 11:48 PM, Lars-Magnus Skog notifications@github.com
wrote:

@mikolalysenko https://github.com/mikolalysenko Might be hard to check
this, since it might load on the machine building the binaries but not on
another machine.

You could use https://github.com/juliangruber/require-rebuild to have it
be rebuilt on the target machine if the require fails


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#65 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL3MBq_o1bp9CHVFE3XhjPxwj28L9jpks5qnQyygaJpZM4Ione3
.

@tehbelinda
Copy link

tehbelinda commented Oct 10, 2016

Here's what worked for me in more detail:

  1. Set up the system dependencies sudo apt-get install -y build-essential libxi-dev libglu1-mesa-dev libglew-dev (That was for Ubuntu, see https://github.com/stackgl/headless-gl#system-dependencies)
  2. Set up the dev environment, i.e. follow steps 1-6 of https://github.com/stackgl/headless-gl#how-should-i-set-up-a-development-environment-for-headless-gl (Note for step 6 I had to do npm run rebuild instead of npm run build)
  3. Copy and replace the built webgl.node file into your node module, e.g. cp headless-gl/build/Release/webgl.node node_modules/gl/build/Release/webgl.node

@nina124
Copy link

nina124 commented Mar 12, 2018

hi, @tehbelinda
I followed your instruction, however got stuck in the step 3: cp headless-gl/build/Release/webgl.node node_modules/gl/build/Release/webgl.node
I did not find the folder node_modules/gl/build/Release/webgl.node under the minos root. And I also checked no node_modules folder in the src code.
Do you created it or is it under other path?

@tehbelinda
Copy link

Hi @nina124 this would be where ever you ran npm install to set up the node modules originally. I'm guessing you are here from the 2 issues linked above, so looking at those, it seems like the part that's run in node is in the minos/server path so try looking in there? If not, then you might want to try checking with minos if there's something wrong with the npm setup

@nina124
Copy link

nina124 commented Mar 15, 2018

Thanks @tehbelinda
Problem solved!

@dhritzkiv
Copy link
Member

Closing as part of clean up. Feel free to re-open this issue.

@fcard
Copy link

fcard commented Aug 22, 2020

I have gotten this problem and recompiling from the source did not solve it.
npm test also fails at this point:

✓ limits_gl-max-texture-dimensions55Aborted (core dumped)
not ok 5838 no plan found
⨯ fail 1

So it might be something specific to my pc hardware/configuration, if that's not supposed to happen? Should I open another issue?

My OS is Linux/Ubuntu Mate (Ubuntu 20.04, with kernel 5.4.0-42), architecture is Amd64.

@Karang
Copy link

Karang commented Jan 11, 2021

I had the same issue, and solved it using npm rebuild --build-from-source gl

@trusktr
Copy link

trusktr commented Feb 28, 2021

An alternative is the webgl-raub package, which worked out of the box without --build-from-source for me.

@entrptaher
Copy link

I solved this with this package.json example.

{
  "name": "video-generation",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "editly": "^0.14.2"
  },
  "overrides": {
    "editly": {
      "gl": "https://github.com/stackgl/headless-gl.git"
    }
  }
}

And then,

cd node_modules/gl && yarn rebuild

It was not working for me otherwise.

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

No branches or pull requests