Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: freshy98 <freshy98@gmx.net>
Cc: Kumba <kumba@gentoo.org>, Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: IPTables 1.3.x fails on RaQ2
Date: Mon, 07 Mar 2005 23:35:18 -0800	[thread overview]
Message-ID: <422D55B6.4010300@jg555.com> (raw)
In-Reply-To: <422D4A49.9020504@gmx.net>

I found the culprit, but don't know what the proper fix is.

File - What to remove or comment out
/usr/src/linux/include/asm/cpu-features.h - #include 
<cpu-feature-overrides.h>
/usr/src/linux/include/asm/addrspace.h -  #include <spaces.h>

But it still fails, because it looks at the headers in /usr/include and 
the ones is /usr/src/linux/include, which is what the problem is. Namely 
socket.h

What I noticed is some of the mips architectures includes have these 
files and some do not.

A workaround for those who use the linux-libc-headers to build iptables 
with the following commands, but I would still comment out those files 
to prevent other build issues later

make KERNEL_DIR=/usr

But I'm not sure of the stability and the functionality.

-- 
----
Jim Gifford
maillist@jg555.com

  reply	other threads:[~2005-03-08  7:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 17:20 IPTables 1.3.x fails on RaQ2 Jim Gifford
2005-03-07 17:37 ` freshy98
2005-03-08  2:26   ` Kumba
2005-03-08  4:20     ` Jim Gifford
2005-03-08  5:40       ` Kumba
2005-03-08  6:46         ` freshy98
2005-03-08  7:35           ` Jim Gifford [this message]
2005-03-08 13:24             ` Ralf Baechle
2005-03-08 16:30               ` Jim Gifford
2005-03-08 16:37                 ` Ralf Baechle
2005-03-08 13:46             ` Kumba

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=422D55B6.4010300@jg555.com \
    --to=maillist@jg555.com \
    --cc=freshy98@gmx.net \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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