On Wed, Oct 04, 2017 at 09:09:51AM -0700, Doug Anderson wrote: > Hi, > > On Tue, Oct 3, 2017 at 9:07 PM, Guenter Roeck <groeck@xxxxxxxxxx> wrote: > > On Tue, Oct 3, 2017 at 8:20 PM, Masahiro Yamada > >> CC: for building tools that run on the target machine > >> HOSTCC: for building tools that run on the build machine > >> > >> > >> IMHO, this should be consistent to avoid confusion. > >> > >> > >> Grepping CROSS_COMPILE under tools/ directory, > >> I see many Makefile expect CC for the target system. > >> > >> For ex, tools/croup/Makefile > >> > >> CC = $(CROSS_COMPILE)gcc > >> > >> > >> > >> Why don't you fix tools/objtool/Makefile ? > >> > >> > > > > Interesting question. You are right, most tools are target tools, not > > host tools. Maybe it _would_ make sense to use HOSTCC/HOSTCFLAGS to > > build it. Copying Josh for input. Yes, converting objtool to use HOSTCC/HOSTCFLAGS etc would be a good improvement. It has a dependency on libsubcmd, so tools/lib/subcmd/Makefile will also need to be changed (and be careful not to break perf in the process). > Ah, good point. I'm not terribly familiar with the things under > tools, so when I saw "objtool" I assumed it was following a standard > pattern for tools. > > I can submit a patch for objtool's Makefile. ...or, if it makes more > sense, I can submit a patch to move "objtool" to the scripts > directory. ...or I can butt out of it. :) Which would folks prefer? In some ways objtool would be a more natural fit in the scripts dir. However, we decided to put it in tools because it might be useful outside of the kernel and it's much easier to extract it from the kernel that way. Also, it has a shared dependency on libsubcmd with perf, which is also in tools. -- Josh -- 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
