public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bart dot vanassche at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2859] New: linux/i2c.h header contains kernel-only definitions Date: Wed, 28 Jun 2006 07:54:00 -0000 [thread overview] Message-ID: <20060628075407.2859.bart.vanassche@gmail.com> (raw) The header <linux/i2c.h> is provided by glibc and is needed from user-space because it contains the definitions of e.g. I2C_TENBIT, I2C_SLAVE, ... However, it contains many declarations and definitions that only make sense when included from within the kernel, and that make no sense in user-space (e.g. i2c_master_send(), struct i2c_driver). Additionally, user-space C source files that include <linux/i2c.h> do not compile. -- Summary: linux/i2c.h header contains kernel-only definitions Product: glibc Version: 2.3.3 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: bart dot vanassche at gmail dot com CC: glibc-bugs at sources dot redhat dot com GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=2859 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-06-28 7:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-28 7:54 bart dot vanassche at gmail dot com [this message] 2006-06-28 7:57 ` [Bug libc/2859] " bart dot vanassche at gmail dot com 2006-06-28 14:34 ` aj at suse dot de
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=20060628075407.2859.bart.vanassche@gmail.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).