From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Generating unistd_*.h
Date: Tue, 30 Aug 2011 14:12:04 -0700 [thread overview]
Message-ID: <4E5D5224.5000400@zytor.com> (raw)
In-Reply-To: <4E5D501D.9000604@zytor.com>
[Cc: dwmw2]
On 08/30/2011 02:03 PM, H. Peter Anvin wrote:
> On 08/30/2011 01:16 PM, H. Peter Anvin wrote:
>> On 08/27/2011 04:48 AM, H. Peter Anvin wrote:
>>> 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.
>>>>
>>
>> OK, got things mostly working, but I'm a bit stuck on how to make
>> headers-install do the right thing. objhdr-y doesn't seem to deal with
>> the generated subdirectory very well, and we don't really want the files
>> *installed* into the generated subdirectory for user space.
>>
>> Any suggestions for how to best handle it?
>>
>
> For reference, putting the following in arch/x86/include/asm/Kbuild does
> *not* work, because $(objtree)/arch/x86/include/asm doesn't exist, and
> so Kbuild generates an invalid path:
>
> objhdr-y += ../generated/asm/unistd_32.h
> objhdr-y += ../generated/asm/unistd_64.h
>
Similarly, overriding obj in the same file does not work, because
scripts/Makefile.headersinst uses $(srctree)/$(obj) not
$(srctree)/$(src) ... is that normal/expected?
-hpa
next prev parent reply other threads:[~2011-08-30 21:12 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
2011-08-30 20:16 ` H. Peter Anvin
2011-08-30 21:03 ` H. Peter Anvin
2011-08-30 21:12 ` H. Peter Anvin [this message]
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=4E5D5224.5000400@zytor.com \
--to=hpa@zytor.com \
--cc=dwmw2@infradead.org \
--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).