linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: _ _ _ _ _ <clangers@toucansurf.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l-utils  undefined symbol: dvb_dev_alloc
Date: Sun, 13 Oct 2019 19:45:36 +0100	[thread overview]
Message-ID: <2FBA3FCF-6ADA-42F2-A422-8BA602AD7B01@toucansurf.com> (raw)
In-Reply-To: <20191012150220.1bff18ed@coco.lan>

I originally built using
./configure --prefix=/usr --sysconfdir=/etc --disable-static && make

so adapting your instructions and putting /usr/lib in /etc/ld.so.conf.d/local.conf and then executing ldconfig were the essential steps that fixed it.

Thanks.

> On 12 Oct 2019, at 19:02, Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> 
> Em Sat, 12 Oct 2019 18:28:41 +0100
> _ _ _ _ _ <clangers@toucansurf.com> escreveu:
> 
>> 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.
> 
> Shouldn't have any real consequence. it is just because there's nothing
> like:
> 
> 	ret = ftruncate(...)
> 	if (ret) {
> 		/* some error handling logic */
> 	}
> 
>> 
>> 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
> 
> Probably you have an older version of DVB libraries installed on
> your machine. It is trying to use the older library when you try
> to run it.
> 
> There are some ways of solving it:
> 
> 1) Make configure to override the old library with:
> 
> 	./configure --prefix=/usr
> 
> (the default is to install it at /usr/local)
> 
> 2) Ensure that the dynamic linker will use the libraries from
> /usr/local
> 
> Depending on how your distro is set, you could need to add a
> new file at /etc/ld.so.conf.d/, in order to teach the dynamic
> linker to use the /usr/local/lib directory to seek for libraries.
> 
> For example, create a "/etc/ld.so.conf.d/local.conf" file, and make the
> system use it by running, as root:
> 
> 	# echo "/usr/local/lib" > /etc/ld.so.conf.d/local.conf
> 	# ldconfig 
> 
> PS.: You may need to remove a previous install of the V4L and DVB
> libs, in order to avoid any conflicts.
> 
> 3) use the environment var LD_LIBRARY_PATH in order to add 
> /usr/local/lib to the list of directories it will seek for a 
> library.
> 
> Thanks,
> Mauro


      parent reply	other threads:[~2019-10-13 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 17:28 v4l-utils undefined symbol: dvb_dev_alloc _ _ _ _ _
2019-10-12 18:02 ` Mauro Carvalho Chehab
2019-10-12 18:47   ` _ _ _ _ _
2019-10-13 18:45   ` _ _ _ _ _ [this message]

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=2FBA3FCF-6ADA-42F2-A422-8BA602AD7B01@toucansurf.com \
    --to=clangers@toucansurf.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+samsung@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).