Re: [PATCH 2/2] s390: boot, purgatory: pass $(CLANG_FLAGS) where needed

2019-04-14 Thread Martin Schwidefsky
On Thu, 11 Apr 2019 11:08:31 -0700 Nick Desaulniers wrote: > On Thu, Apr 11, 2019 at 1:52 AM Arnd Bergmann wrote: > > > > On Thu, Apr 11, 2019 at 12:14 AM 'Nick Desaulniers' via Clang Built > > Linux wrote: > > > On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote: > > > > > > > > The purg

Re: [PATCH 2/2] s390: boot, purgatory: pass $(CLANG_FLAGS) where needed

2019-04-11 Thread Nick Desaulniers
On Thu, Apr 11, 2019 at 1:52 AM Arnd Bergmann wrote: > > On Thu, Apr 11, 2019 at 12:14 AM 'Nick Desaulniers' via Clang Built > Linux wrote: > > On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote: > > > > > > The purgatory and boot Makefiles do not inherit the original cflags, > > > so clang fal

Re: [PATCH 2/2] s390: boot, purgatory: pass $(CLANG_FLAGS) where needed

2019-04-11 Thread Arnd Bergmann
On Thu, Apr 11, 2019 at 12:14 AM 'Nick Desaulniers' via Clang Built Linux wrote: > On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote: > > > > The purgatory and boot Makefiles do not inherit the original cflags, > > so clang falls back to the default target architecture when building it, > > typ

Re: [PATCH 2/2] s390: boot, purgatory: pass $(CLANG_FLAGS) where needed

2019-04-10 Thread Nick Desaulniers
On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote: > > The purgatory and boot Makefiles do not inherit the original cflags, > so clang falls back to the default target architecture when building it, > typically this would be x86 when cross-compiling. > > Add $(CLANG_FLAGS) everywhere so we pass

[PATCH 2/2] s390: boot, purgatory: pass $(CLANG_FLAGS) where needed

2019-04-10 Thread Arnd Bergmann
The purgatory and boot Makefiles do not inherit the original cflags, so clang falls back to the default target architecture when building it, typically this would be x86 when cross-compiling. Add $(CLANG_FLAGS) everywhere so we pass the correct --target=s390x-linux option when cross-compiling. Si