-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toolchain build scripts #434
Comments
Rating: Wonder+Full |
Sounds great! Go for it. Can you create the empty project under the org, then issue a PR so we can do code review (rather than full blown import)?
Would you mind just putting the license block in a LICENSE file rather than specifying at the top of a new file (I find that a PITA otherwise). |
Sure to both. |
The scripts were rewritten in Python, if people want to give it a test. |
Updated the wiki accordingly: https://github.com/ClangBuiltLinux/linux/wiki/Building-Clang-from-source |
Since the BPF_PROG_TYPE_CGROUP_SOCKOPT verifier test does not set an attach type, bpf_prog_load_check_attach() disallows loading the program and the test is always skipped: #434/p perfevent for cgroup sockopt SKIP (unsupported program type 25) Fix the issue by setting a valid attach type. Fixes: 0456ea1 ("bpf: Enable more helpers for BPF_PROG_TYPE_CGROUP_{DEVICE,SYSCTL,SOCKOPT}") Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com> Link: https://lore.kernel.org/bpf/20200710150439.126627-1-jean-philippe@linaro.org
I've gone ahead and created a set of build scripts to build LLVM,
clang
,ld.lld
, and binutils from source. This was inspired by issues like #337 (which spawned our wiki page), #358, and this thread. This can help get people involved (since I've designed it to be fairly self contained by default so people don't have to arbitrarily add repos to their package manager to get a newer build ofclang
/ld.lld
).The repo is here: https://github.com/nathanchance/tc-build
I'd like to bring this into our organization and I am happy to take ownership of it, I just want people to be okay with that and review it to see if there are any major objections.
The text was updated successfully, but these errors were encountered: