The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Penshoppe Estrada <penshoppe@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel compile Error
Date: Fri, 19 May 2006 11:15:47 +0200	[thread overview]
Message-ID: <20060519091547.GA10077@stusta.de> (raw)
In-Reply-To: <20060519074536.95542CA0A4@ws5-11.us4.outblaze.com>

On Fri, May 19, 2006 at 03:45:36PM +0800, Penshoppe Estrada wrote:
> Hello,
> 
> Good Day!
> 
> Anyone could help me with this error. Thanks in advance.
> 
> 
>   CC      net/netfilter/xt_string.o
>   CC      net/netfilter/xt_tcpmss.o
>   LD      net/netfilter/built-in.o
>   CC      net/netlink/af_netlink.o
> net/netlink/af_netlink.c: In function `netlink_release':
> net/netlink/af_netlink.c:472: error: structure has no member named `protinfo'
> net/netlink/af_netlink.c:472: error: structure has no member named `protinfo'
> net/netlink/af_netlink.c:473: error: structure has no member named `protocol'
> net/netlink/af_netlink.c:474: error: structure has no member named `protinfo'
>...
> [root@ja linux-2.6.16]#
>...

You seem to have a corrupted source tree.

Please try with a fresh linux-2.6.16.16.tar.gz from ftp.kernel.org 
without any additional patches applied.

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:[~2006-05-19  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  7:45 Kernel compile Error Penshoppe Estrada
2006-05-19  9:15 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-09  2:15 kernel compile error Rodrigo F. Baroni
2003-01-09  2:48 ` Joshua Kwan
2001-10-13 16:34 Kernel " Tobias Hahn

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=20060519091547.GA10077@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penshoppe@linuxmail.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