linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kbuild@vger.kernel.org
Subject: Generating unistd_*.h
Date: Fri, 26 Aug 2011 17:20:48 -0700	[thread overview]
Message-ID: <4E583860.5080603@zytor.com> (raw)

I am working on a patchset after which unistd_*.h in the x86 tree will
be autogenerated by scripts.  This is a substantial cleanup and a
preparation for the x32 setup.

However, one consequence of this is that <asm/unistd.h> will now include
a number of autogenerated fragments, some of which will be needed by
"make headers-install".  Furthermore, since <asm/asm-offsets.h> depends
on <asm/unistd.h> this creates a new dependency which I'm not sure what
the best way to handle is from a kbuild perspective.

1. Is there a better place than others to put these generated files
   (i.e. other than $(obj)/arch/x86/include/asm)?

2. Is there a better place than others to put the rules for generate
   these files?

3. There needs to be an arch-specific way to encode the dependency
   before asm-offsets.h is generated.  Preferences here?

	-hpa

             reply	other threads:[~2011-08-27  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-27  0:20 H. Peter Anvin [this message]
2011-08-27 10:18 ` Generating unistd_*.h Sam Ravnborg
2011-08-27 11:48   ` H. Peter Anvin
2011-08-30 20:16     ` H. Peter Anvin
2011-08-30 21:03       ` H. Peter Anvin
2011-08-30 21:12         ` H. Peter Anvin
2011-08-31 14:01           ` Michal Marek
2011-08-31 16:29             ` H. Peter Anvin
2011-11-04  0:54               ` H. Peter Anvin

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=4E583860.5080603@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kbuild@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 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).