public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: e9hack <e9hack@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] compile problems on 2.6.29-rc1
Date: Tue, 13 Jan 2009 21:55:15 +0100	[thread overview]
Message-ID: <496CFFB3.40109@googlemail.com> (raw)
In-Reply-To: <9ac6f40e0901121341h4e447bbxbf26c7ff7153dcc0@mail.gmail.com>

e9hack@googlemail.com schrieb:
> 2009/1/12 e9hack <e9hack@googlemail.com>
>> I've problems to compile the current hg tree with some modifications on
>> linux 2.6.29-rc1.
> 
> 
> It seems, any included file like #include <media/....> uses the file from
> kernel source tree instead of the v4l-dvb tree.

Hi,

I could solve my compile problem with a little patch:

diff -r b09b5128742f v4l/Makefile
--- a/v4l/Makefile      Mon Jan 12 22:50:52 2009 -0200
+++ b/v4l/Makefile      Tue Jan 13 21:45:36 2009 +0100
@@ -161,6 +161,7 @@ ifeq ($(VERSION).$(PATCHLEVEL),2.6)

  # Needed for kernel 2.6.24 or upper
  KBUILD_CPPFLAGS := -I$(SUBDIRS)/../linux/include $(KBUILD_CPPFLAGS) -I$(SUBDIRS)/
+ LINUXINCLUDE := -I$(SUBDIRS)/../linux/include $(LINUXINCLUDE) -I$(SUBDIRS)/

In 2.6.28.1 LINUXINCLUDE is part of KBUILD_CPPFLAGS of the kernel. In 2.6.29-rc1
LINUXINCLUDE is part of the command line for gcc. LINUXINCLUDE is include before
KBUILD_CPPFLAGS.

Regards,
Hartmut

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

      reply	other threads:[~2009-01-13 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 20:31 [linux-dvb] compile problems on 2.6.29-rc1 e9hack
2009-01-12 21:41 ` e9hack
2009-01-13 20:55   ` e9hack [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=496CFFB3.40109@googlemail.com \
    --to=e9hack@googlemail.com \
    --cc=linux-dvb@linuxtv.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