Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756890AbcJTHi1 (ORCPT ); Thu, 20 Oct 2016 03:38:27 -0400 Received: from mout.web.de ([212.227.17.12]:61595 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755850AbcJTHiY (ORCPT ); Thu, 20 Oct 2016 03:38:24 -0400 Subject: Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation To: Segher Boessenkool References: <4f2251fc-94ee-41d3-cc03-a39cee5a084c@users.sourceforge.net> <1238ba8e-a297-6de5-2e6a-50e6e72e77d3@users.sourceforge.net> <4fe8b518-6145-5322-a852-beeb61abd559@users.sourceforge.net> <20161019220346.GA20054@gate.crashing.org> Cc: Jim Davis , linux-kbuild@vger.kernel.org, Michal Marek , linux-kernel , kernel-janitors@vger.kernel.org From: SF Markus Elfring Message-ID: <80d31faa-b328-b8eb-4d19-d96aef1cc16a@users.sourceforge.net> Date: Thu, 20 Oct 2016 09:37:34 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161019220346.GA20054@gate.crashing.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:f3QFkNOBfwYC80kSiELi6b0FKa3xdeYu7/10ubrrkE1XG60AxPH DiA7NHgPi4pmjsY0t+89CiPHCbI9BnH368WTgE774WodHl5QfZhTzHzx4VqMSC3560A70nW gpq3U9cI5AP1ItI7XFl1PHVvhZWV8H9AIeaHD7P+hW4GWC2cZxtKxwjZ76bbUoKdvoYJpjo yvA7YfhGDkd93VMoohtJQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:uKD8YfAEFr0=:o35b7pS/u1kpKKec/ZG6SJ 4qQpPHbQAF5FmokL8kPnx+7PEVl+3bqfjKGE4jAYzSio/Hbv7A4AV//U0vEnMbwbytGS1euKK AFYkjAziO80HNaIZvrI3NRJ5EvCuYZqMoIoaqEmvV/wvYKn1lVJeHULnCdf3chZgKzqTg1oum MaihKn83LiLWT/ro5oI1nKOriRupesSm09Dr9wyXreAUVEqrDok57TlzW1iSo4rmkCgLBRNry NWHuXklVXfzXqg7sbUX05jguP5ZFqLr7o6c3QhCZkhqJFfaV9OWG+xa5tR7PtkYNZ61WcLJaV HFFP+RHXoKWBCKFGoTA/iBb4YRDxMLzuoV1uBSjKLkKxueRV25ktq3ktGdSY81k0hRVCKQeCa avxHkcXHo/aqaR73On4XhS+ts5d3FwEH75J2HmqqDPmZcPmnTfeKGcP4UdiYwh13UKZ01tEFK kGUwcwNcY5Ak3pXDFOqyiwjq+qZ2nzwzwKeSKjPvcNjr83Kj66u70YL3syXfk/jFxQ2n3yOCV sKTyoWcvksls54wfHalBfVApdp2Lfhi3hdOwH8VIewsH0YTwaGhSqbjqe1A6wXze/Ay0p+gF8 0e3X8pXC4+nhxkLywMUAqXmrY+T00lqRpiGU8S2zlH68pL4yxpONklrZil32nwoieMwYeVrQv iZCvrQPX3ZgVuqq+W+yVMWOv/QzDMnEqcjq+/Qzif8cZKFSOKWW9PNf6sRQa84BvXtgYIL8b4 qWQDbFpAzQHSV8fmO8MB9vcxleLoK+gJHRf75KQDufg2nRuQHFpeg2/sNLaVkWWzpWOxuE4Jj v6Qk1dd Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1233 Lines: 38 > Don't forget -r when running objdump on an object file. Thanks for your reminder. > But, you want to use make drivers/md/whatever.s if you want to see > the assembler code. Thanks for your advice! This is one kind of "generation convenience" I was looking for. Was my software development attention too limited for another moment so that I did not directly pick an opportunity up from the description like "dir/file.[ois] - Build specified target only" (by the command "make help") that I can get assembler source files for Linux modules so easy on demand? Would you like to point any places out in the make scripts which show relevant commands for such build targets? > And that doesn't work for build-time tools, I got the impression that they can trigger further software development challenges. Should their source files (and corresponding make parameters) be improved anyhow? > which I think is what the original discussion was about. I see a few change possibilities there. Will it be useful to reconsider the generation parameters for build-time tools in comparison to components from other Linux software areas? Will a variable like "EXTRA_CFLAGS" achieve a desired effect at more places? Regards, Markus