From: _ _ _ _ _ <clangers@toucansurf.com>
To: linux-media@vger.kernel.org
Cc: Clangers <clangers@toucansurf.com>
Subject: v4l-utils undefined symbol: dvb_dev_alloc
Date: Sat, 12 Oct 2019 18:28:41 +0100 [thread overview]
Message-ID: <35A2C1D4-DE40-490C-AFE6-E426EC1EC0AC@toucansurf.com> (raw)
I've been waiting for a working version of DVB-S2 capable tools and utilities to appear in a stable release of Mint\x10, but it hasn't happened yet, so I decided to build the latest stable v4l-utils from source.
I built v4l-utils version 1.18.0 on Linux Mint 18.3
the compilation process appeared to run through OK with only 9 warnings (see below), but the resulting executables fail due to a lib ref issue.
configure: WARNING: doxygen not found - will not generate any doxygen documentation
configure: WARNING: libelf library not available
configure: WARNING: Qt5 or higher is not available
configure: WARNING: ALSA library not available
CC control/libv4lconvert_la-libv4lcontrol.lo
control/libv4lcontrol.c: In function ‘v4lcontrol_create’:
control/libv4lcontrol.c:728:3: warning: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Wunused-result]
ftruncate(shm_fd, V4LCONTROL_SHM_SIZE);
^
libtool: warning: relinking 'libv4l2.la'
libtool: warning: relinking 'v4l2convert.la'
libtool: warning: relinking 'libv4l1.la'
libtool: warning: relinking 'v4l1compat.la'
Most of these look insignificant but the fifth one looks a bit worrying.
End result :-
stupiduser@somehost ~ $ gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 2016060
stupiduser@somehost ~ $ dvbv5-scan -V
dvbv5-scan version 1.18.0
stupiduser@somehost ~ $ dvbv5-scan /usr/share/dvb/dvb-s/Astra-28.2E
dvbv5-scan: symbol lookup error: dvbv5-scan: undefined symbol: dvb_dev_alloc
stupiduser@somehost ~ $ dvb-fe-tool -m -a0
dvb-fe-tool: symbol lookup error: dvb-fe-tool: undefined symbol: dvb_dev_alloc
- - - - - - - -
I've appended a bunch of links that refer to C versus C++ declarations.
Is it really necessary for me "a user" to change all the source code references to the suggested form just to get it work.
Surely there must be a stupid mistake that I've made instead.
Refs to the compiler declaration issues:
https://stackoverflow.com/questions/53322164/linking-shared-library-libdvbv5-undefined-reference
https://stackoverflow.com/questions/18877437/undefined-reference-to-errors-when-linking-static-c-library-with-c-code
https://stackoverflow.com/questions/1041866/what-is-the-effect-of-extern-c-in-c/1041880#1041880
https://github.com/gjasny/v4l-utils/blob/master/lib/libdvbv5/dvb-fe.c
next reply other threads:[~2019-10-12 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 17:28 _ _ _ _ _ [this message]
2019-10-12 18:02 ` v4l-utils undefined symbol: dvb_dev_alloc Mauro Carvalho Chehab
2019-10-12 18:47 ` _ _ _ _ _
2019-10-13 18:45 ` _ _ _ _ _
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35A2C1D4-DE40-490C-AFE6-E426EC1EC0AC@toucansurf.com \
--to=clangers@toucansurf.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).