linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Generating unistd_*.h
Date: Sat, 27 Aug 2011 04:48:42 -0700	[thread overview]
Message-ID: <4E58D99A.2050400@zytor.com> (raw)
In-Reply-To: <20110827101820.GA2990@merkur.ravnborg.org>

On 08/27/2011 03:18 AM, Sam Ravnborg wrote:
>>
>> 1. Is there a better place than others to put these generated files
>>    (i.e. other than $(obj)/arch/x86/include/asm)?
> $(obj)/arch/x86/include/generated
> 
> This is what generic-y supports uses.
> 
>>
>> 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?
> 
> Use "archprepare".
> 
> Something like this in arch/x86/Makefile:
> 
> archprepare: arch/x86/tools/syscall-magic.sh
> 	$(CONFIG_SHELL) $<
> 
> It should IIRC be execute before we try to create asm-offsets.h.
> So there is no dependency issues.
> 

I'll try this and see how it works out.  Sounds quite clean.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2011-08-27 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=4E58D99A.2050400@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.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).