From: Steffen Barszus <steffenbpunkt@googlemail.com>
To: Scott <igetmyemailhere@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Compiling v4l fatal error: linux/ti_wilink_st.h: No such file or directory
Date: Tue, 8 Mar 2011 08:51:07 +0100 [thread overview]
Message-ID: <20110308085107.7bcb52ef@grobi> (raw)
In-Reply-To: <FBB75E3F-418B-470F-8169-25CC3AFBA73F@gmail.com>
On Mon, 7 Mar 2011 17:22:39 -0600
Scott <igetmyemailhere@gmail.com> wrote:
>
> Same problem. I purged both linux-headers-2.6.35-27-generic,
> linux-source-2.6.35, then reinstalled them, and did an apt-get
> update/upgrade. I then deleted media_build and ran...
linux-headers should be enough, no need for linux-source, and you need
never both IMHO.
> git clone git://linuxtv.org/media_build.git
> cd media_build
> ./build.sh
> Compile breaks
> vi vrl/.config changed CONFIG_DVB_FIREDTV=m to =n
should not be necessary anymore, at least its not needed here.
> ./build.sh
You might want to try my dkms package - not sure if it works on
maverick (its build on/for lucid) - but in theory it should (except
if the number of modules differs for different kernel).
If not you get atleast the latest source which compiles fine here.
https://launchpad.net/~yavdr/+archive/testing-vdr/+packages?field.name_filter=v4l-dvb-dkms&field.status_filter=published&field.series_filter=
Just uploaded new version with media_build and media_tree as of now.
Let me know if it works.
Steffen
prev parent reply other threads:[~2011-03-08 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 19:01 Compiling v4l fatal error: linux/ti_wilink_st.h: No such file or directory Me
2011-03-07 21:57 ` Jarod Wilson
[not found] ` <AANLkTim52X9Y=BpGi9fjiNy1hGgVRNdRjwYWPkNDTRBU@mail.gmail.com>
2011-03-07 23:17 ` Jarod Wilson
2011-03-07 23:22 ` Scott
2011-03-08 7:51 ` Steffen Barszus [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=20110308085107.7bcb52ef@grobi \
--to=steffenbpunkt@googlemail.com \
--cc=igetmyemailhere@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox