Comparing make V=1 with the suggested config before my patch, after my
patch, and after Masahiro's suggestion to add $(LDFLAGS):
before:
...
ld -m elf_i386 -pie-T arch/x86/boot/compressed/vmlinux.lds ...
...
after my:
...
ld -m elf_i386 -T arch/x86/boot/compressed/vmlinux.lds ...
...
af
That's safe to do for now. Here's the 0-day failure thread:
https://lists.01.org/pipermail/lkp/2017-October/007427.html If I can
sort out the issue, I'll submit a v3.
On Mon, Oct 30, 2017 at 8:46 AM, Masahiro Yamada
wrote:
> 2017-10-30 15:50 GMT+09:00 Masahiro Yamada :
>> 2017-10-29 0:00 GMT+09
2017-10-30 15:50 GMT+09:00 Masahiro Yamada :
> 2017-10-29 0:00 GMT+09:00 Masahiro Yamada :
>> 2017-10-28 5:13 GMT+09:00 Nick Desaulniers :
>>> I was not seeing my linker flags getting added when using ld-option when
>>> cross compiling with Clang. Upon investigation, this seems to be due to
>>> a d
2017-10-29 0:00 GMT+09:00 Masahiro Yamada :
> 2017-10-28 5:13 GMT+09:00 Nick Desaulniers :
>> I was not seeing my linker flags getting added when using ld-option when
>> cross compiling with Clang. Upon investigation, this seems to be due to
>> a difference in how GCC vs Clang handle cross compilat
2017-10-28 5:13 GMT+09:00 Nick Desaulniers :
> I was not seeing my linker flags getting added when using ld-option when
> cross compiling with Clang. Upon investigation, this seems to be due to
> a difference in how GCC vs Clang handle cross compilation.
>
> GCC is configured at build time to suppo
I was not seeing my linker flags getting added when using ld-option when
cross compiling with Clang. Upon investigation, this seems to be due to
a difference in how GCC vs Clang handle cross compilation.
GCC is configured at build time to support one backend, that is implicit
when compiling. Clan
6 matches
Mail list logo
