Do not pretend to be a GNU/Linux

[alex]

Based on rust-lang/rust#62698

[geofft]

FWIW, torvalds/linux@5f074f3 (v5.1) adds a bcmp that's implemented as memcmp, saying specifically that this LLVM change broke upstream clang targets. So,

1. Should we put this back once we can assume 5.1+?
2. Do the upstream kernel clang targets use unknown-linux-gnu and if so should we do the same?

[alex]

Excellent question, don't know!

[geofft]

Poking around a bit more, https://github.com/ClangBuiltLinux/linux/wiki/Steps-for-compiling-the-kernel-with-Clang It seems the Makefile doesn't do anything super conditional, they're just using clang as a cc.

Should we suggest that the upstream clang build cross-compile to foo-elf instead of compiling for the native platform / foo-unknown-linux-gnu?

[alex]

That seems like it'd be an honorable contribution to usptream, if you know how to do such a thing :-)

…

On Sun, Aug 4, 2019 at 10:47 PM Geoffrey Thomas ***@***.***> wrote: Poking around a bit more, https://github.com/ClangBuiltLinux/linux/wiki/Steps-for-compiling-the-kernel-with-Clang It seems the Makefile doesn't do anything super conditional, they're just using clang as a cc. Should we suggest that the upstream clang build cross-compile to foo-elf instead of compiling for the native platform / foo-unknown-linux-gnu? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#114?email_source=notifications&email_token=AAAAGBDZYG5BVOS3L5EFJ33QC6IC7A5CNFSM4IJGZP7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3QRCAA#issuecomment-518066432>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAAGBF5GSE7KGCYM4IJC5TQC6IC7ANCNFSM4IJGZP7A> .

-- All that is necessary for evil to succeed is for good people to do nothing.

[nickdesaulniers]

#147 (comment)