From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from terminus.zytor.com ([198.137.202.10]:41736 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752920Ab1H0AUz (ORCPT ); Fri, 26 Aug 2011 20:20:55 -0400 Message-ID: <4E583860.5080603@zytor.com> Date: Fri, 26 Aug 2011 17:20:48 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 Subject: Generating unistd_*.h Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: linux-kbuild@vger.kernel.org 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 will now include a number of autogenerated fragments, some of which will be needed by "make headers-install". Furthermore, since depends on 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