[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210331161552.GG25400@brightrain.aerifal.cx>
Date: Wed, 31 Mar 2021 12:15:53 -0400
From: Rich Felker <dalias@...c.org>
To: Thierry Gayet <thierry.gayet@...zl.tv>
Cc: musl@...ts.openwall.com
Subject: Re: missing symbol from musl libc
On Wed, Mar 31, 2021 at 05:36:38PM +0200, Thierry Gayet wrote:
> Hi,
>
> I use musl within alpine.
>
> in this environment I have an open source package based on Chromium (in C /
> C ++) which needs to be recompiled.
>
> The compilation step goes well but at the link step, the linker cannot find
> certain symbols from the libc:
> hread_getattr_np@...BC_2.2.5'
> /usr/lib/gcc/x86_64-alpine-linux-musl/10.2.1/../../../../x86_64-alpine-linux-musl/bin/ld:
> .../third_party/cef/cef_binary_75.0.6+g90ecd35+chromium-75.0.3770.80_linux64/Release/libcef.so:
> undefined reference to `snd_pcm_sw_params_set_avail_min@...A_0.9'
> /usr/lib/gcc/x86_64-alpine-linux-musl/10.2.1/../../../../x86_64-alpine-linux-musl/bin/ld:
> .../third_party/cef/cef_binary_75.0.6+g90ecd35+chromium-75.0.3770.80_linux64/Release/libcef.so:
> undefined reference to `mbsrtowcs@...BC_2.2.5'
> ...
I'm not 100% sure because everything around the Chromium build process
is so obfuscated and contrary to reasonable build practices, but it
looks like you just have a binary library someone shipped that was
linked against glibc, and that's using glibc symbol versioning. For
both of those reasons it's very unlikely to be suitable to link with
musl. If you can build it from source, for a musl-based target, I
would expect the problems to go away.
Rich
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.
