From: Daniel Jacobowitz <dan@debian.org>
To: dkegel <dkegel@google.com>
Cc: Andrew Morton <akpm@osdl.org>,
Markus Gutschke <markus@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386
Date: Fri, 10 Mar 2006 18:40:10 -0500 [thread overview]
Message-ID: <20060310234010.GA6549@nevyn.them.org> (raw)
In-Reply-To: <545d88bc0603091936i5c25c065ne8e31ca23e9473f4@mail.google.com>
On Thu, Mar 09, 2006 at 07:36:25PM -0800, dkegel wrote:
> On 3/9/06, Andrew Morton <akpm@osdl.org> wrote:
> > I doubt if glibc is borrowing the kernel's macros.
>
> I think it is, though.
>
> When I build gcc/glibc toolchains, I have to use kernel headers.
> I used to directly use the ones in the kernel.org tree, but
> those aren't quite intended for use in userspace; fortunately,
> Mariusz Mazur's sanitized kernel headers work great.
>
> I'd like to see these patches go in to the sanitized kernel headers
> and/or the kernel.org tree. I imagine that putting them in the kernel.org
> tree is right, and they'd naturally percolate from there to the
> various sanitized headers projects.
It uses the headers for many things. It does not use the _syscallX
macros.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-10 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 23:33 [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386 Markus Gutschke
2006-03-10 2:47 ` Andrew Morton
2006-03-10 3:03 ` Markus Gutschke
2006-03-10 3:22 ` Andrew Morton
2006-03-10 3:36 ` dkegel
2006-03-10 23:40 ` Daniel Jacobowitz [this message]
2006-03-10 23:53 ` dkegel
2006-03-10 22:42 ` [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386 (updated patch) Markus Gutschke
2006-03-10 23:02 ` dkegel
2006-03-11 0:05 ` [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386 Arnd Bergmann
2006-03-10 14:37 ` Jan Engelhardt
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=20060310234010.GA6549@nevyn.them.org \
--to=dan@debian.org \
--cc=akpm@osdl.org \
--cc=dkegel@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@google.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 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.