[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150628102324.62f825e3@r2lynx>
Date: Sun, 28 Jun 2015 10:23:24 +0700
From: Рысь <lynx@...server.ru>
To: musl@...ts.openwall.com
Subject: Re: Fwd: Link problems with static node-canvas
On Sun, 28 Jun 2015 01:10:23 +0200
"piranna@...il.com" <piranna@...il.com> wrote:
> > have you verified that
> > Release/obj.target/static/jpeg.a
> > Release/obj.target/static/freetype.a
> > have the missing symbols?
> > (eg using nm)
>
> I have checked them with nm -u and they are defined, although as
> "undefined"... What does this means? The output tell they are
> "undefined" in the .o file that is defining them... :-/
>
> P.D.: sorry for so much questions, this things are totally new to
> me... :-(
>
>
That's normal, for example I've taken one symbol from `nm -u` and
checked it just with `nm` and this symbol is properly defined:
% nm /local/lib/libjpeg.a | fgrep jpeg_alloc_huff_table
U jpeg_alloc_huff_table
000000b0 T jpeg_alloc_huff_table
U jpeg_alloc_huff_table
U jpeg_alloc_huff_table
Just other object files inside library are referencing this symbol and
have source object file with this symbol as dependency and ld inserts
it into final executable/shared object. That's why `nm` reports them as
undefined.
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.
