public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Gert Vervoort <gert.vervoort@hccnet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22: dvb header files break compilation on x86-64
Date: Wed, 11 Jul 2007 18:02:54 +0200	[thread overview]
Message-ID: <20070711160254.GH3492@stusta.de> (raw)
In-Reply-To: <4691F8D6.30600@hccnet.nl>

On Mon, Jul 09, 2007 at 10:59:02AM +0200, Gert Vervoort wrote:
>
> Some of the linux/dvb header files include libc header files and break 
> compilation on x86-64 in compat_ioctl.c:
>
>
>   CC      fs/timerfd.o
>   CC      fs/eventfd.o
>   CC      fs/compat.o
>   CC      fs/compat_ioctl.o
> In file included from fs/compat_ioctl.c:111:
> include/linux/dvb/audio.h:27:20: error: stdint.h: No such file or directory
> In file included from fs/compat_ioctl.c:112:
> include/linux/dvb/dmx.h:28:18: error: time.h: No such file or directory
> make[1]: *** [fs/compat_ioctl.o] Error 1
> make: *** [fs] Error 2
> [root@apollo linux-2.6.x]#

According to the line numbers your build is pulling a version of the 
header cleaned for userspace.

Does this happen with a freshly unpacked vanilla 2.6.22 kernel from 
ftp.kernel.org?

Please send the first 50 lines of the file include/linux/dvb/audio.h in 
your kernel sources.

What is the output of "make V==1" for fs/compat_ioctl.o?

>    Gert

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-07-11 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09  8:59 2.6.22: dvb header files break compilation on x86-64 Gert Vervoort
2007-07-11 16:02 ` Adrian Bunk [this message]
2007-07-11 18:59   ` Gert Vervoort

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=20070711160254.GH3492@stusta.de \
    --to=bunk@stusta.de \
    --cc=gert.vervoort@hccnet.nl \
    --cc=linux-kernel@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