version `GLIBC_2.29' not found

[Jacques-Olivier Haché]

Hi all,

I'm facing a link/run issue with libwebrtc.

I'm building against M89, commit e7d9f74b. I'm running Ubuntu 16.04.

I can build and link my app, no issue, but when I try to run it, I get the following issue:

> ./out/Default/myApp

./out/Default/myApp: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./out/Default/myApp)

If I do a check on my libm, I don't believe it depends on libc 2.29. See:

> ldd /lib/x86_64-linux-gnu/libm.so.6

linux-vdso.so.1 =>  (0x00007fff1ac1c000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9e9ade8000)

/lib64/ld-linux-x86-64.so.2 (0x00007f9e9b4bb000)

> ll /lib/x86_64-linux-gnu/libc.so.6

lrwxrwxrwx 1 root root 12 Jan 15  2018 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.23.so*

I did check the build tools inside of build/linux/debian_sid_amd64-sysroot/lib/x86_64-linux-gnu/, and I do see libc-2.29.so. However even adding this folder to my path didn't help.

Is there anything that I am clearly doing wrong? Why would my app try to use a different libc.so.6 than the one listed by ldd?

Thanks,

JOH

[peks geshkov]

---

This email and any files transmitted with it are for the sole use of the intended recipient and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply email and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this email is strictly prohibited and may be unlawful. Thank you for your cooperation.

---

2020, Temasys (www.temasys.io)

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/a9d8d1a4-9198-4444-abee-a090c895e7afn%40googlegroups.com.

Try include :

LIBS     = (other libs....) -lgobject-2.0 -lglib-2.0 -lpthread

[Jacques-Olivier Haché]

Hi, 

Thanks for your answer. 

I did try, but to no avail. Actually these flags were already in the link command. See:

> ninja -C out/Default/ myApp -j 16 -v
ninja: Entering directory `out/Default/'
[0/1] ../../buildtools/linux64/gn --root=../.. -q --regeneration gen .
[1/1] python "../../build/toolchain/gcc_link_wrapper.py" --output="./myApp" -- ../../third_party/llvm-build/Release+Asserts/bin/clang++ ../../../../third_party/ffmpeg/lib/libevent.a ../../../../third_party/ffmpeg/lib/libavfilter.a ../../../../third_party/ffmpeg/lib/libpostproc.a ../../../../third_party/ffmpeg/lib/libevent_pthreads.a ../../../../third_party/ffmpeg/lib/libamqpcpp.a -L../../../../third_party/ffmpeg/lib/ -lavcodec -lavformat -lavutil -lavfilter -lswscale -lswresample -lcurl -L../../../../third_party/boost/lib/ -lboost_system -lboost_date_time -lboost_random -fuse-ld=lld -Wl,--build-id -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -Wl,--color-diagnostics -Wl,--no-call-graph-profile-sort -m64 -Wl,--gdb-index -rdynamic -nostdlib++ --sysroot=../../build/linux/debian_sid_amd64-sysroot -L../../build/linux/debian_sid_amd64-sysroot/usr/local/lib/x86_64-linux-gnu -L../../build/linux/debian_sid_amd64-sysroot/lib/x86_64-linux-gnu -L../../build/linux/debian_sid_amd64-sysroot/usr/lib/x86_64-linux-gnu -pie -Wl,--disable-new-dtags -o "./myApp" -Wl,--start-group @"./myApp.rsp" -Wl,--end-group -ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lX11 -lXext -lGL -lm

[Aaron Clauson]

Installing an updated version of the stdlib solved it for me (I'm pretty sure the custom stdlib the libwebrtc build uses is later than what comes installed on Ubuntu 16.04):

sudo apt install libstdc++-9-dev libevent-dev

Full steps I used https://github.com/sipsorcery/webrtc-echoes/blob/master/libwebrtc/README.md#building-libwebrtc-fulla-on-ubuntu

[Jacques-Olivier Haché]

Hi Aaron,

Thanks for your advice. Unfortunately, it didn't fix it either.

Now, I did something I should have done a long time ago: I tried to build a hello world app and build it with ninja, and it worked. I then made it create a PeerConnectionFactory and it worked as well.

That leads me think that there is something else that is breaking my app's dependency. Either

- Using PeerConnectionFactory doesn't link against the the relevant webrtc dependency that creates the issue, or

- I have an additional third party dependency, and that's the one creating the issue.

I link against my own ffmpeg, but I've already checked, and that links and runs successfully. I will check for my other dependencies one by one.

Can anyone clarify whether I'd need to actually use a webrtc module to trigger that dependency to libm?

Thanks!