Re: Generating unistd_*.h

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[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
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux&nblp;USB Development]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite Secrets]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux