From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] 2.10.1: No rule to make target `asm/io.h',
Date: Tue, 26 Sep 2006 18:56:48 +0000 [thread overview]
Message-ID: <20060926205648.6e5a58d0.khali@linux-fr.org> (raw)
In-Reply-To: <20060926135555.GH10410@neu.nirvana>
> > No, it looks like /usr/include/asm/io.h was recently dropped.
>
> Ah, looking at the previous (current) release the contents of asm/io.h
> are
>
> | #ifndef _ASM_IO_H
> | #define _ASM_IO_H
> |
> | #warning <asm/io.h> is deprecated, use <sys/io.h> instead
> | #include <sys/io.h>
> |
> | #endif
I found some posts along these lines on the web. However, I take that
you never saw this warning, because our code reads:
/* To keep glibc2 happy */
#if defined(__GLIBC__) && __GLIBC__ = 2 && __GLIBC_MINOR__ >= 0
#include <sys/io.h>
#else
#include <asm/io.h>
#endif
So it should look for sys/io.h rather than asm/io.h. It does for me.
I suspect that the test on __GLIBC__ somehow fails for you. Can you
please give a try to the following program?
--- 8< ---
#include <stdio.h>
int main()
{
printf("__GLIBC__ = %d\n", __GLIBC__);
printf("__GLIBC_MINOR__ = %d\n", __GLIBC_MINOR__);
return 0;
}
--- 8< ---
$ gcc -Wall -W test_glibc.c -o test_glibc
I expect some surprise on your FC6 system.
That being said the test above looks bogus to me, the test on
__GLIBC_MINOR__ is useless as far as I can see, and the test will break
on GLIBC 3 for sure.
--
Jean Delvare
next prev parent reply other threads:[~2006-09-26 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 13:55 [lm-sensors] 2.10.1: No rule to make target `asm/io.h', Axel Thimm
2006-09-26 17:12 ` Jean Delvare
2006-09-26 18:37 ` Axel Thimm
2006-09-26 18:47 ` Axel Thimm
2006-09-26 18:56 ` Jean Delvare [this message]
2006-09-26 19:08 ` Axel Thimm
2006-09-26 20:17 ` Jean Delvare
2006-09-30 17:17 ` Axel Thimm
2006-10-01 0:40 ` Axel Thimm
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=20060926205648.6e5a58d0.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.