From: Song Wang <wsonguci@yahoo.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: asm-mips/processor.h breaks compiling user applications such as iptables
Date: Thu, 15 Jul 2004 19:01:47 -0700 (PDT) [thread overview]
Message-ID: <20040716020147.71295.qmail@web40005.mail.yahoo.com> (raw)
In-Reply-To: <20040715225657.GA17585@linux-mips.org>
--- Ralf Baechle <ralf@linux-mips.org> wrote:
> On Thu, Jul 15, 2004 at 03:22:34PM -0700, Song Wang
> wrote:
>
> > I think the error is due to the line 146
> >
> > typedef u64 fpureg_t;
> >
> > The type 'u64' is defined in asm-mips/types.h, but
> > wrapped by #ifdef __KERNEL__, so when the compiler
> > compiles the user-level application, it cannot
> > recognize u64.
>
> Correct. In general the policy is to avoid the use
> of kernel header
> files in user space and copy it but there are still
> a few crucial tools
> that don't follow this rule of Linus, so try below
> patch. It also
> removes the __KERNEL__ things left.
>
> Cleaning up the use of kernel header to make them
> more usable for
> userspace is one of the things on the agenda for
> 2.7. It'll be alot of
> hard and boring work but MIPS will be one of the
> architectures that will
> greatly benefit from this.
>
> Ralf
>
Hi, Ralf
I tested the patch and it compiles fine now, although
when iptables actually runs on mips32, all the
tcp/udp port numbers are shown as 0 and IP address
shown as 0.0.0.0. I'll dig more.
Anyway, you made a good point for kernel headers
problem. It's kinda headache.
Similar problem happened to asm-mips/page.h when
including <spaces.h> in 2.6.6, but it seemed that
you already fixed in the latest cvs version.
Thanks.
-Song
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
prev parent reply other threads:[~2004-07-16 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 22:22 asm-mips/processor.h breaks compiling user applications such as iptables Song Wang
2004-07-15 22:56 ` Ralf Baechle
2004-07-16 2:01 ` Song Wang [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=20040716020147.71295.qmail@web40005.mail.yahoo.com \
--to=wsonguci@yahoo.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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