From: Logan Gunthorpe Sent: November 6, 2018 at 8:01:31 PM GMT > To: Nadav Amit <na...@vmware.com>, Ingo Molnar <mi...@redhat.com> > Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x...@kernel.org>, Sam > Ravnborg <s...@ravnborg.org>, Michal Marek <michal.l...@markovi.net>, Thomas > Gleixner <t...@linutronix.de>, H. Peter Anvin <h...@zytor.com>, Linux Kbuild > mailing list <linux-kbu...@vger.kernel.org>, Stephen Bates > <sba...@raithlin.com> > Subject: Re: [PATCH v9 02/10] Makefile: Prepare for using macros for inline > asm > > > > > On 2018-11-06 12:18 p.m., Nadav Amit wrote: >> Err.. I don’t have a dist-cc environment. I wonder whether something like >> that would do the trick: > > I tested it to be sure -- but, no, this does not have any affect on > distcc. Distcc usually does pre-processing locally and then sends the > single output of cpp to a remote for compilation and assembly. It > doesn't expect there to be additional assembly files tacked on the > command line and isn't going to handle that case correctly. Thus, > changing the path of the file won't fix anything.
Thanks for the explanation. I played with dist-cc and gave it some thought, but I do not have a solution. I thought that perhaps some hack is possible by using the same preprocessed file can be used as both the source file and the assembly file, but that’s as far as I managed to get. Ideas? Do people care about it?
