All of lore.kernel.org
 help / color / mirror / Atom feed
From: e9hack <e9hack@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] compile error
Date: Fri, 18 Apr 2008 19:35:59 +0200	[thread overview]
Message-ID: <4808DBFF.9020600@gmail.com> (raw)

Hi,

compiling of the current hg tree fails with the following message:

   CC [M]  /usr/src/v4l-dvb/v4l/flexcop-pci.o
In file included from /usr/src/v4l-dvb/v4l/flexcop-common.h:12,
                  from /usr/src/v4l-dvb/v4l/flexcop-pci.c:10:
/usr/src/v4l-dvb/v4l/compat.h:539: error: static declaration of 'proc_create' follows 
non-static declaration
/usr/src/linux-2.6.25/include/linux/proc_fs.h:128: error: previous declaration of 
'proc_create' was here
make[5]: *** [/usr/src/v4l-dvb/v4l/flexcop-pci.o] Error 1

This patch does fix the problem:

diff -r 6aa6656852cb v4l/compat.h
--- a/v4l/compat.h      Wed Apr 16 13:13:15 2008 -0300
+++ b/v4l/compat.h      Fri Apr 18 19:33:38 2008 +0200
@@ -533,6 +533,7 @@ do { 
       \
         le16_to_cpu(get_unaligned((unsigned short *)(a)))
  #define put_unaligned_le16(r, a)                               \
         put_unaligned(cpu_to_le16(r), ((unsigned short *)(a)))
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 25)
  #ifdef CONFIG_PROC_FS
  static inline struct proc_dir_entry *proc_create(const char *a,
         mode_t b, struct proc_dir_entry *c, const struct file_operations *d)
@@ -549,5 +550,6 @@ static inline struct proc_dir_entry *pro
  }
  #endif
  #endif
-
-#endif
+#endif
+
+#endif

-Hartmut

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

                 reply	other threads:[~2008-04-18 17:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4808DBFF.9020600@gmail.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 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.