CentOS7 installation of rtpengine with the following error undefined reference to 'av_get_default_channel_layout'
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c, centos
- Domain
- build-system
Research direction
The failing link is for daemon/fix_frame_channel_layout.h (generated by the make rule for lib/fix_frame_channel_layout-04.h); line 9 calls av_get_default_channel_layout, a symbol dropped from newer FFmpeg/libav, so check how the build picks the compatibility header variant. The link line also shows '-L$(exec_prefix)/lib64' and a shell error 'exec_prefix: command not found', so inspect the Makefile's libav/pkg-config detection and library paths. Done means the daemon links on this CentOS 7 setup, either with the FFmpeg version this rtpengine release expects or the matching fix_frame_channel_layout variant.
Written by the indexing model from the issue text.
Description
hi:
I have the following error when installing rtpengine in centos source code
My installed version:
rtpengine-mr10.3.1.7
cc -g -Wall -Wextra -Wno-sign-compare -Wno-unused-parameter -Wstrict-prototypes -pthread -fno-strict-aliasing -std=c99 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/libxml2 -I/usr/include/libxml2 -pthread -I/usr/include/json-glib-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DWITH_IPTABLES_OPTION -I. -I../kernel-module/ -I../lib/ -I../include/ -D_GNU_SOURCE -DWITH_TRANSCODING -I/usr/include/mysql -DRE_PLUGIN_DIR=""/usr/lib/rtpengine"" -DHAVE_BCG729 -I/usr/local/include/ -DHAVE_MQTT -DRTPENGINE_VERSION=""undefined"" -rdynamic fix_frame_channel_layout-test.c -lm -lglib-2.0 -pthread -lgthread-2.0 -lglib-2.0 -lz -lpcre -lcrypto -lssl -lcrypto -levent_pthreads -levent -lpcap -lxmlrpc_client -lxmlrpc -lxmlrpc_util -lhiredis -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lwebsockets -lip4tc -lip6tc -L$(exec_prefix)/lib64 -lspandsp -ltiff -lm -L/usr/lib64/mysql -lmysqlclient -lpthread -lz -lm -ldl -lssl -lcrypto -L/usr/local/lib64/ -lbcg729 -lmosquitto -o fix_frame_channel_layout-test
/bin/sh: exec_prefix: command not found
/tmp/ccWDDX8n.o: In function fix_frame_channel_layout':
/root/rtpengine-mr10.3.1.7/daemon/fix_frame_channel_layout.h:9: undefined reference to av_get_default_channel_layout'
collect2: error: ld returned 1 exit status
make[3]: *** [fix_frame_channel_layout-test] Error 1
make[3]: Leaving directory /root/rtpengine-mr10.3.1.7/daemon'
Failed build with ../lib/fix_frame_channel_layout-04.h
make[2]: *** [fix_frame_channel_layout.h] Error 1
rm sdp.strhash.c control_ng.strhash.c call_interfaces.strhash.c janus.strhash.c
make[2]: Leaving directory /root/rtpengine-mr10.3.1.7/daemon'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/rtpengine-mr10.3.1.7/daemon'
make: *** [all] Error 2
How can I solve it?thank you
- Dominant language
- Perl
- Stars
- 992
- Forks
- 459
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sipwise/rtpengine
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 3 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 3 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
sipwise/rtpengine#2197 · 1 comment ·
Maintainers usually reply within 3 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
sipwise/rtpengine#2190 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sipwise/rtpengine#2181 · 4 comments ·
Maintainers usually reply within 3 days
All issues in sipwise/rtpengine
Similar issues
-
documentation Needs Triage
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Proposed Text EditsOpen
Difficulty 1/5 Under an hour Newbie friendliness 82/100
curl/everything-curl#658 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
PDLPorters/pdl#561 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/eolang.sty#197 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
radiator-software/p5-net-ssleay#577 ·
Maintainers usually reply within 1 day