Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756940AbcJRQup (ORCPT ); Tue, 18 Oct 2016 12:50:45 -0400 Received: from mail-io0-f173.google.com ([209.85.223.173]:35795 "EHLO mail-io0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753537AbcJRQui (ORCPT ); Tue, 18 Oct 2016 12:50:38 -0400 MIME-Version: 1.0 In-Reply-To: <1238ba8e-a297-6de5-2e6a-50e6e72e77d3@users.sourceforge.net> References: <4f2251fc-94ee-41d3-cc03-a39cee5a084c@users.sourceforge.net> <1238ba8e-a297-6de5-2e6a-50e6e72e77d3@users.sourceforge.net> From: Jim Davis Date: Tue, 18 Oct 2016 09:50:36 -0700 Message-ID: Subject: Re: Difficulties around "fixdep" for the usage of a kernel build output directory To: SF Markus Elfring Cc: linux-kbuild@vger.kernel.org, Michal Marek , linux-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id u9IGonO7012250 Content-Length: 1237 Lines: 31 On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring wrote: >>> elfring@Sonne:~/Projekte/Linux/next-patched> my_off=-O0 && for X in off; do my_output_dir=${my_build_dir}unchanged/optimisation/${X} && my_var="my_${X}" && my_parameters="-Wall -std=gnu89 -fomit-frame-pointer ${!my_var}" && LANG=C make V=2 O="${my_output_dir}" HOSTCC='/usr/bin/gcc-6' HOSTCFLAGS="-S ${my_parameters}" drivers/md/; done > … >> That's a very complicated command line. > > I find it "advanced". > > It shows a few of my imaginations around a specific software development task. > > >> Does something basic, like >> >> make O=/tmp/$$ allmodconfig >> make O=/tmp/$$ >> >> work for you? > > Not really. - I would like to achieve the automatic selection of a few > compilation settings by a for loop which I reduced in the shown example > to one element. Fine, but my point was to check that the basic things worked before trying the complicated, or "advanced" stuff. 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. And if fixdep did work with a basic setup , then that would suggest something wrong with your advanced command line. -- Jim