Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965157AbcJRR0Q (ORCPT ); Tue, 18 Oct 2016 13:26:16 -0400 Received: from mout.web.de ([212.227.17.11]:59276 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752675AbcJRR0I (ORCPT ); Tue, 18 Oct 2016 13:26:08 -0400 Subject: Re: Difficulties around "fixdep" for the usage of a kernel build output directory To: Jim Davis References: <4f2251fc-94ee-41d3-cc03-a39cee5a084c@users.sourceforge.net> <1238ba8e-a297-6de5-2e6a-50e6e72e77d3@users.sourceforge.net> Cc: linux-kbuild@vger.kernel.org, Michal Marek , linux-kernel From: SF Markus Elfring Message-ID: Date: Tue, 18 Oct 2016 19:25:59 +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: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:pp+x58mntpn4eAW2DvslAvFQ/za5v/fTXfntoF/859zi2RecwFx qjFdqb7XtFI05jfb27HaCgFvggwWfpuLP4PtrSsBvMdKuqlsXyw0zOkzu/bTdniZcrOX9CV qu9Icjw1CZ8LuV/qW6LAvAoqhz67Na7r6xTQW56IZFB3xCNtGpwSwb3X3m4DXNjtHbMa89V Htg8ro6QulAw8ySblZo7g== X-UI-Out-Filterresults: notjunk:1;V01:K0:WRS6o9uGyO0=:R4U5dt/N5RqhooOfjBS0Kh fjS4amCVMpV+kAsJKOmv23d6f4JerEVKplxfdeahvM3mywmCTxV7jZPIHt064coGbTT+dS3lj KMnrNjjDOteGq8TDToKm239pRm5pugeHvdhLF3cQtHNAIrmAox8zpUaIRVIX9dkuCLThAq07W 1lU1OvY/k0RdKmbz5BJHPygA2JNUmlfT75age3QhqvlXVmhMsJH7tgjAYjF+32ycyL8salMAf SeipQXNn7YGJbehOMfe++U7jiTjS2ontFHM/6dTZMmMc/MwZ6URjWOCFL0oZHQrb+Gjxyqrol LHehBMaliLiKRaEAxTBMcdGt9QXLFGu9ZZVjAHjNjciAoJNZCjUN4FA+fb71Wz/tiapWipaeM 2y6+tnNqAjLBKu0lEXAxgWq9dYG+xRHp4lLKqRY5rGdrKHd2rmy0+06+OoaLyFCIBI6cR2Bd/ UEX78mMUXb9sk3Dj09byLk4O1vjCCS0kT5BeWUqNpVXwxXjRR+SMW7Hq0tYJcmYAzLoACT7dW 3KM1F4A33nedVZLsuNmtd/TGyUFFHblLHGgmWgfvB5mPoJj77zQfe/VELiY+fXfAdKEkuvM6+ dwKjprjmpoyjWPrwj2BwAhFhVc9uvGSEhUbJx+qPqi0rZL363JIdKl+grGX53mF64bz9Gwe9D VqL55dsE9b0ZaeVc2HP7CzxrB2LtnGpqxzxtKeFESEaBtIYpR28z+G9J4SMP33b+MiJdpffhI xKXKPagmWItC4yhNkFMFXxV8y47K4j5uTaiDaQL7I1V6q8cG99l+daCgKmYQ6u/bEMUZzPiEu l5E83Ft Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1107 Lines: 27 > Fine, but my point was to check that the basic things worked before > trying the complicated, or "advanced" stuff. Your suggestion is fine in this sense. I can observe that the following command variant works as expected here. my_build_dir=/tmp/fixdep-check-20161018-1 && mkdir "${my_build_dir}" && my_cc=/usr/bin/gcc-6 && make O="${my_build_dir}" HOSTCC="${my_cc}" allmodconfig && make -j6 O="${my_build_dir}" HOSTCC="${my_cc}" drivers/md/ > If, somehow, fixdep didn't work in a basic setup then you'd know it wasn't one of your > advanced features that was causing the problem. The command example above is an approximation for the configuration approach which I would really want instead. > And if fixdep did work with a basic setup , then that would suggest > something wrong with your advanced command line. How do you think about to clarify further which implementation detail could trigger the shown software build difficulty? Can it be that the passing of the adjusted parameter "HOSTCFLAGS" has got a significant influence (with unwanted side effects) in this use case? Regards, Markus