linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Generating unistd_*.h
@ 2011-08-27  0:20 H. Peter Anvin
  2011-08-27 10:18 ` Sam Ravnborg
  0 siblings, 1 reply; 9+ messages in thread
From: H. Peter Anvin @ 2011-08-27  0:20 UTC (permalink / raw)
  To: linux-kbuild

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2011-11-04  1:00 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-27  0:20 Generating unistd_*.h H. Peter Anvin
2011-08-27 10:18 ` 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

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).