Date: Sun, 28 Jun 2015 00:05:19 +0200 From: "piranna@...il.com" <piranna@...il.com> To: musl@...ts.openwall.com Subject: Re: Link problems with static node-canvas > just seems to work because the symbols weren't used, but as > soon as they are, the code will crash.. (because lazy binding) Didn't though about it... [piranna@...uk:~/Proyectos/node-canvas] (master) > node examples/font.js node: symbol lookup error: /home/piranna/Proyectos/node-canvas/build/Release/canvas.node: undefined symbol: FT_Init_FreeType ...but seems you are right, the Ubuntu-glibc compilation have the same problem, only that lazy binding didn't showed it before. > whatever the link command was add -ljpeg and -lwhateverwasmissing > to the end I've tried this with no result, also by adding the -L argument and using directly the filename and path to the .a files. Also, the generated linker command makes use of --start-group and --end-group, that according to the docs iterates over the object files instead of doing only one pass until all the undefined entries are resolved... other thing is that if this is a no-op while building a dynamic library since some of the entries would be always undefined and resolved in other place... Anyway, by adding the libraries at the end as you suggested it should have work... :-/ -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.