Mirror of forum.nim-lang.org

6133 :: libvapoursynth.so: undefined symbol: pthread_create

• mantielero (orginal) [2020-03-30T15:32:06+02:00] view original

  Tonight I updated my archlinux installation. It updated vapoursynth from R48 to R49.

  If I compile and run a file I get the message:

  $ ./modifyframe
  /home/jose/src/VapourSynth.nim/src/libs/libvapoursynth.so: undefined symbol: pthread_create
  could not load: /home/jose/src/VapourSynth.nim/src/libs/libvapoursynth.so

  But if I run one of the files compiled before the update it works fine.

  Any clue about what might be happening?

---

• geotre (orginal) [2020-03-30T15:44:24+02:00] view original

  Did you compile with --threads:on?

---

• mantielero (orginal) [2020-03-30T15:47:14+02:00] view original

  That fails, but I have checked that the following works:

  nim c -f --threads:on --gc:none modifyframe

  Why do I need that now? Is this a change in Nim or in vapoursynth? I keep on using v1.0.6 as far as I know.

---

• geotre (orginal) [2020-03-30T16:00:51+02:00] view original

  Do you mean that without --gc:none you get the error above?

---

• mantielero (orginal) [2020-03-30T16:03:29+02:00] view original

  A different one. I get a Segfault:

---

• geotre (orginal) [2020-03-30T16:27:00+02:00] view original

  Can you paste the error? Seems most likely that something changed in the vapoursynth update and now your bindings don't match up

---

• mantielero (orginal) [2020-03-30T16:51:46+02:00] view original

  It doesn't gives me much information:

  $ ./modifyframe
  Violación de segmento (`core' generado)

  I have observed also that this happens when I call a macro, but not when I call a vapoursynth plugin.

---

• mantielero (orginal) [2020-03-31T16:49:30+02:00] view original

  Solved in Archlinux's R49-2. It was a packaging problem.

---