All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Atwood <williamatwood41@gmail.com>
To: LMML <linux-media@vger.kernel.org>
Subject: Failure of ./build
Date: Sat, 04 Feb 2017 22:41:45 -0500	[thread overview]
Message-ID: <58969EF9.2000703@gmail.com> (raw)

I am attempting to build the V4L-DVB Device Drivers according to 
https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

The build stops with a failure message, the last few lines of which are 
shown in the following extract:

No file to patch.  Skipping patch.
1 out of 1 hunk ignored
make[2]: *** [apply_patches] Error 1
make[2]: Leaving directory `/home/bill/V4L/media_build/linux'
make[1]: *** [allyesconfig] Error 2
make[1]: Leaving directory `/home/bill/V4L/media_build/v4l'
make: *** [allyesconfig] Error 2
can't select all drivers at ./build line 490.
bill@willow:~/V4L/media_build$

I am running Ubuntu 14.04.1 LTS.  (I recently tried to update to 16.04 
LTS, but it fails for some obscure reason.)  My kernel is 
3.13.0-108-generic.

My capture card is a Hauppauge WinTV HVR 955Q, and it is plugged in. 
The device ID is 2040:b123 Hauppauge.

I understand the basics of using "make" and am well familiar with 
Linux/Ubuntu use, but these messages tell me nothing.  I would be happy 
to upload the entire output from the build, but I am reluctant to put 
all 273 lines in this message.

Can anyone suggest an approach to resolving my problem?

   Bill

             reply	other threads:[~2017-02-05  3:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05  3:41 Bill Atwood [this message]
     [not found] ` <CAEsFdVM=d5x-ekuvQ9BtkzanPtRmZgOwkL_f4Z2UMPLT+roDzg@mail.gmail.com>
2017-02-05  4:15   ` Failure of ./build Vincent McIntyre

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=58969EF9.2000703@gmail.com \
    --to=williamatwood41@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.