Linux Media Controller development
 help / color / mirror / Atom feed
From: Dominik Danelski <dominik@danelski.pl>
To: <linux-media@vger.kernel.org>
Subject: Problem with compilation prevents me from adding a new device
Date: Tue, 21 May 2019 22:20:15 +0200	[thread overview]
Message-ID: <1558470015.3271.4@pro1.mail.ovh.net> (raw)

Hello,

I found this 
guide:https://www.onetransistor.eu/2017/05/magix-usb-videowandler-2-linux.html 
which explains how to get Magix Videowandler 2 as an audio-video 
source. It is achieved by downloading drivers from LinuxTV project, 
slightly modifying them and installing. I wanted to incorporate changes 
from the guide to the upstream code, but first I wanted to test 
everything once again. I tried to follow the described method of 
compiling drivers (before making any changes) and I got stuck with a 
following output:
  CC [M]  /tmp/media_build/v4l/videobuf-core.o
  CC [M]  /tmp/media_build/v4l/videobuf-dma-sg.o
/tmp/media_build/v4l/videobuf-dma-sg.c: In function 
'videobuf_dma_init_user_locked':
/tmp/media_build/v4l/videobuf-dma-sg.c:190:17: error: 'FOLL_LONGTERM' 
undeclared (first use in this function); did you mean 'FOLL_FORCE'?
         flags | FOLL_LONGTERM, dma->pages, NULL);
                 ^~~~~~~~~~~~~
                 FOLL_FORCE
/tmp/media_build/v4l/videobuf-dma-sg.c:190:17: note: each undeclared 
identifier is reported only once for each function it appears in

What could have caused it? I suppose that the code already in the 
repository has been checked and such thing should not happen if not by 
my mistake, but I did not change anything after cloning git repo.

Regards
Dominik Danelski


             reply	other threads:[~2019-05-21 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 20:20 Dominik Danelski [this message]
2019-05-22  0:42 ` Problem with compilation prevents me from adding a new device Mauro Carvalho Chehab

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=1558470015.3271.4@pro1.mail.ovh.net \
    --to=dominik@danelski.pl \
    --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