Re: Link problems with static node-canvas

[Szabolcs Nagy <nsz@port70.net>]

* ???????? <lynx@sibserver.ru> [2015-06-27 17:07:28 +0700]:
> There are more undefined symbols than listed on your screenshot, but
> musl reports only one (maybe that's related to dynlinker overhaul), in
> particular from Freetype there are 20 of them, and jinit_arith_encoder,
> also related to jpeg.
> 

what's worse is that it most likely broken with glibc too

just seems to work because the symbols weren't used, but as
soon as they are, the code will crash.. (because lazy binding)

> If you link in static libraries than you should, like with static
> programs, order your dependency list (the order of static libraries).
> Since ld does not generate any link errors when making shared object
> and treat any undefined symbol like it will come later it's hard to do
> that right when you don't know your library internals well (and you're
> not with bigger ones such as jpeg, png and freetype). What's your final
> link command?
> 

this is most likely the issue

whatever the link command was add -ljpeg and -lwhateverwasmissing
to the end