From: David Daney <ddaney@caviumnetworks.com>
To: Dok Sander <doksander@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-mips <linux-mips@linux-mips.org>
Subject: Re: io.h doesn't get installed by target "headers_install" for mips
Date: Wed, 09 Sep 2009 11:17:23 -0700 [thread overview]
Message-ID: <4AA7F133.20104@caviumnetworks.com> (raw)
In-Reply-To: <806810.23677.qm@web59313.mail.re1.yahoo.com>
Dok Sander wrote:
> Hi,
>
> I noticed the absence of the header io.h while trying to build(cross-compile, host i686-pc-linux-gnu) a software(lm-sensors-3.1.1, wants io.h in /sys) for mips. I can find io.h for mips in arch/mips/asm/include/{,sn/} However, io.h doesn't get installed when i do "make ARCH=mips headers_install" on linux 2.6.30.6
>
> According to someone on the eglibc mailing list, linux should provide io.h for mips. Is this true?
>
I don't think so (for two reasons):
1) The things in /usr/include/sys are provided by libc not the kernel.
2) MIPS doesn't have I/O ports, so all the functions in sys/io.h on an
x86 are undefined for MIPS.
David Daney
parent reply other threads:[~2009-09-09 18:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <806810.23677.qm@web59313.mail.re1.yahoo.com>]
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=4AA7F133.20104@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=doksander@yahoo.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).