Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Rosario Pingaro" <rpingar@italycom.it>
To: netfilter@lists.netfilter.org
Subject: Re: compilation problem rhat el4
Date: Sat, 13 Aug 2005 14:47:19 -0400	[thread overview]
Message-ID: <002e01c5a037$6edb2bf0$0401a8c0@casa> (raw)
In-Reply-To: 001601c5a028$5c89d500$23d8b2d5@iserver1

when I run "make KERNEL_DIR=/usr/src/linux" it gets the right extensions:
Extensions found: IPv4:CLUSTERIP IPv4:layer7 IPv4:recent IPv6:ah IPv6:esp 
IPv6:f
rag IPv6:ipv6header IPv6:hbh IPv6:dst IPv6:rt

when I run "make KERNEL_DIR=/usr" it gets only IPv4:recent

I think for this reason I don't have layer7's module compiled.

I need help, step by step on how to fix the "error including kernel header 
in userspace; use the glibc headers instead! make"

Hope some one can help.
Thanks
Rosario


----- Original Message ----- 
From: "Rosario Pingaro" <rpingar@italycom.it>
To: <netfilter@lists.netfilter.org>
Sent: Saturday, August 13, 2005 12:59 PM
Subject: compilation problem rhat el4


I would like to have the l7-filter funtionality on my redhat el4.

So I downloada the latest iptable-1.3.3 and the last patch from l7-filter

But trying to compile the patched files I get this error:
#error including kernel header in userspace; use the glibc headers instead! 
make: *** [extensions/libipt_layer7_sh.o] Error 1

I found several posts about it without any useful solution.
In fact if I use "KERNEL_DIR=/usr" I get the header from userspace so 
everything is compiled but not the layer7 module "libipt_layer7.so".

I checked if everything into the kernel (about packet filtering and layer7) 
is activated, and there, everythings seems fine.

Just to note that "libipt_layer7.h" is not present on my system.

Where is my problem?

Thanks
Rosario




      reply	other threads:[~2005-08-13 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13 16:59 compilation problem rhat el4 Rosario Pingaro
2005-08-13 18:47 ` Rosario Pingaro [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='002e01c5a037$6edb2bf0$0401a8c0@casa' \
    --to=rpingar@italycom.it \
    --cc=netfilter@lists.netfilter.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