From: Ralf Baechle <ralf@linux-mips.org>
To: Jim Gifford <maillist@jg555.com>
Cc: freshy98 <freshy98@gmx.net>, Kumba <kumba@gentoo.org>,
Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: IPTables 1.3.x fails on RaQ2
Date: Tue, 8 Mar 2005 13:24:08 +0000 [thread overview]
Message-ID: <20050308132408.GB9811@linux-mips.org> (raw)
In-Reply-To: <422D55B6.4010300@jg555.com>
On Mon, Mar 07, 2005 at 11:35:18PM -0800, Jim Gifford wrote:
> 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.
These headers are search along a search path until found. Typically that
path consists of two directories such as mach-ip22 followed by mach-generic
as last. This allows eleminating duplicated header files.
A bad side effect - users frequently forget adding files such as
cpu-features-override.h which contain a detailed description of the CPU
properties on a particular platform. Without a platform specific file
the kernel will basically fallback to generic code that is slow but
supports almost every CPU in the universe.
Ralf
next prev parent reply other threads:[~2005-03-08 13:26 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
2005-03-08 13:24 ` Ralf Baechle [this message]
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=20050308132408.GB9811@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=freshy98@gmx.net \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=maillist@jg555.com \
/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