public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timmy Douglas <timmy+lkml@cc.gatech.edu>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Brian Gerst <bgerst@didntduck.org>, linux-kernel@vger.kernel.org
Subject: Re: macro in linux/compiler.h pollutes gcc __attribute__ namespace
Date: Wed, 04 May 2005 22:08:46 -0400	[thread overview]
Message-ID: <87br7qv2z5.fsf@mail.gatech.edu> (raw)
In-Reply-To: <FBE10E17-C501-4182-9B51-554A37362D10@mac.com> (Kyle Moffett's message of "Wed, 4 May 2005 16:55:53 -0400")

Kyle Moffett <mrmacman_g4@mac.com> writes:

> On May 4, 2005, at 14:10:21, Timmy Douglas wrote:
>> I'm guessing it goes sort of like this:
>>
>> signal.h -> bits/sigcontext.h -> asm/sigcontext.h -> linux/compiler.h
>
> Installing headers directly from the kernel has been deprecated for
> quite a while.  Please look for the "linux-kernel-headers" package
> in whatever your package management system is.  It has a set of
> cleaned headers.  IIRC, there were some proposals a while back for
> how to fix this and make a set of headers useable from userspace,
> but nothing substantial ever got done.

Thanks for the input. It seems this is a gentoo bug then because it
leaves this #define in their version of the source (even though it
removes some other things). I don't see this problem on a debian box I
have though. Too bad this wasn't standardized on.

Thanks again.


      reply	other threads:[~2005-05-05  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 17:35 macro in linux/compiler.h pollutes gcc __attribute__ namespace Timmy Douglas
2005-05-04 17:46 ` Brian Gerst
2005-05-04 18:10   ` Timmy Douglas
2005-05-04 20:55     ` Kyle Moffett
2005-05-05  2:08       ` Timmy Douglas [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=87br7qv2z5.fsf@mail.gatech.edu \
    --to=timmy+lkml@cc.gatech.edu \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox