Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3105499pxb; Tue, 19 Jan 2021 14:03:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJwOJjNrhRmVMps9qA8XhM0AllMgrVWgODpICSc7pJgdPjNncCpW2mjGmJ3EjuTC+R7CHqAC X-Received: by 2002:a17:906:398c:: with SMTP id h12mr4347431eje.469.1611093806934; Tue, 19 Jan 2021 14:03:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611093806; cv=none; d=google.com; s=arc-20160816; b=PzY3tFQFYyPY4h+zFF7+kYksrUVTjQFErPfH+dvP2atZz0nZVauPBrfou55cC0dyH3 lwjs33gwA0aPbtumUkQrvmmE6nAbXeObBaL8Y6Rj7pzHl81i4UczQCGGGP1D2b6lz+sB BaGT30RR+zTUUBUPYpuF55wQc3+z+oRXezLCKcub6geJHyoDTrSfkFuMIqYB9d3Kv6VL Ccd7sCPneqUm/pzs9JoEW/ifH87zouizgjznMsZh16k3rtt1B9JaYv4f0qPKl24b7rKf ADDoOeacil8W/l6UB6cvgseYKBI/IXX0CBN33NYf7k0QEKxWTogcMbmpcfdOl/mXh6jh 6ORw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=OFfub22SWSVkVrjpbdutuEU3cmHlEtcZeAWzURJZldA=; b=GsgUjLB8vlxUt/c4EKaOA1lij2hJ7HS7No9Bgi6xNLCYhkLII3n3karGtuqNt5w5av VCGJ2mbkVntctmaprMnfQ896nlIAKUCEOyWjIugYTLpj2ewtAT3m4M1CSydeDR45ABEy IwGzUcRf/Xy5vHp9PEkgB+xtxsw3+t7dITA+49lAn+VaxjM4fhZtOBmmd0ttKyK+s0Vw QAeNrSxKO3dYSNvD8fWfITcQ38+QMFHkbJk9hYVIOr7oQ8xTAyUGCrR8xDypjRGQ6fd1 GVn/NN0nRY+XYbTxgXJ2v1jfCfpuckTGRjDIRpj0ZUD0StskQo0UmWOjoQ1HhsnzJA7Z hVTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=byWAnMtO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o16si67920edi.480.2021.01.19.14.02.30; Tue, 19 Jan 2021 14:03:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=byWAnMtO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728331AbhASWAa (ORCPT + 99 others); Tue, 19 Jan 2021 17:00:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728414AbhASV7C (ORCPT ); Tue, 19 Jan 2021 16:59:02 -0500 Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A0EBBC061573 for ; Tue, 19 Jan 2021 13:58:19 -0800 (PST) Received: by mail-pg1-x533.google.com with SMTP id 30so13828031pgr.6 for ; Tue, 19 Jan 2021 13:58:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=OFfub22SWSVkVrjpbdutuEU3cmHlEtcZeAWzURJZldA=; b=byWAnMtOBUGykkl0kVkQ6CQf0S8r8iH9Dmayu8mQxBp+45awWTtaLWZK+sCctNvNi6 OQcM7YzgvoQP7vFoUOPAdHcq0Exc8A5qIltWrORr5GlbQu7OpEUlsRIIsRjOPMNEu8MM KJkJ9h2pBNSl3gpKFS1mHwd4Yh8pSmhLhQ+xsdSRbNG79hRNaoSkn4x7kFpQa70zpOTD 2baF8bh7XZpGPB+vYEpB3YYp5CA8M37nZpiDjsHG2HM5Q0fM//zJbXVyQcJhoGFY2/US z2kIqi+reocUHP+UQdZF0D/NV28zsna2hcDSgpI8gW4EXq2SmBmeLi6f+WraBCQVK6ZK 87OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=OFfub22SWSVkVrjpbdutuEU3cmHlEtcZeAWzURJZldA=; b=PyzOgopfhSbx2YYiAax3BGJAuBpIAhQdIknWQzQ34qlIybw5L4WpScqhJADPe34Y6M EnIYXUDkd+sDnXVoyc/0Z7lrsSTZyZPyusKeVu75huVBYrUF/wEH6ErCXB7nirc7vM6B AatJGiFq+PFolX60k/foM/rKIqpFa9ZgWWJk0xkRWPR0RBvJLdoc8bLE2aHw+y77HCcj G+12+TREzYZGio97jWgFLUf3emThyXLXNObTpybFAmZCrORUn3boZp5zB62Q6Xr2KtJ3 r52Hd+FBvYshcBLorstm4nO3UiRB9PyRZTJ6yrU3NE7NCrB6qb2qsQiGiAzYhYe/kzlj o8pA== X-Gm-Message-State: AOAM533pIuee2Vdf8ViGYYCd4niUZVVvjbgr0/du81+xABG0QnEfubkQ BFENG7DbUZWGzRnMwh0iCgf39g== X-Received: by 2002:a63:1f18:: with SMTP id f24mr6316123pgf.133.1611093499079; Tue, 19 Jan 2021 13:58:19 -0800 (PST) Received: from google.com ([2620:15c:2ce:0:a6ae:11ff:fe11:4abb]) by smtp.gmail.com with ESMTPSA id z29sm91002pfk.67.2021.01.19.13.58.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Jan 2021 13:58:18 -0800 (PST) Date: Tue, 19 Jan 2021 13:58:15 -0800 From: Fangrui Song To: Tiezhu Yang Cc: Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Nathan Chancellor , Nick Desaulniers , netdev@vger.kernel.org, bpf@vger.kernel.org, clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org, Xuefeng Li Subject: Re: [PATCH bpf-next v2] samples/bpf: Update README.rst and Makefile for manually compiling LLVM and clang Message-ID: <20210119215815.efyerbwwq5x2o26q@google.com> References: <1611042978-21473-1-git-send-email-yangtiezhu@loongson.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1611042978-21473-1-git-send-email-yangtiezhu@loongson.cn> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-01-19, Tiezhu Yang wrote: >The current llvm/clang build procedure in samples/bpf/README.rst is >out of date. See below that the links are not accessible any more. > >$ git clone http://llvm.org/git/llvm.git >Cloning into 'llvm'... >fatal: unable to access 'http://llvm.org/git/llvm.git/': Maximum (20) redirects followed >$ git clone --depth 1 http://llvm.org/git/clang.git >Cloning into 'clang'... >fatal: unable to access 'http://llvm.org/git/clang.git/': Maximum (20) redirects followed > >The llvm community has adopted new ways to build the compiler. There are >different ways to build llvm/clang, the Clang Getting Started page [1] has >one way. As Yonghong said, it is better to just copy the build procedure >in Documentation/bpf/bpf_devel_QA.rst to keep consistent. > >I verified the procedure and it is proved to be feasible, so we should >update README.rst to reflect the reality. At the same time, update the >related comment in Makefile. > >[1] https://clang.llvm.org/get_started.html > >Signed-off-by: Tiezhu Yang >Acked-by: Yonghong Song >--- > >v2: Update the commit message suggested by Yonghong, > thank you very much. > > samples/bpf/Makefile | 2 +- > samples/bpf/README.rst | 17 ++++++++++------- > 2 files changed, 11 insertions(+), 8 deletions(-) > >diff --git a/samples/bpf/Makefile b/samples/bpf/Makefile >index 26fc96c..d061446 100644 >--- a/samples/bpf/Makefile >+++ b/samples/bpf/Makefile >@@ -208,7 +208,7 @@ TPROGLDLIBS_xdpsock += -pthread -lcap > TPROGLDLIBS_xsk_fwd += -pthread > > # Allows pointing LLC/CLANG to a LLVM backend with bpf support, redefine on cmdline: >-# make M=samples/bpf/ LLC=~/git/llvm/build/bin/llc CLANG=~/git/llvm/build/bin/clang >+# make M=samples/bpf LLC=~/git/llvm-project/llvm/build/bin/llc CLANG=~/git/llvm-project/llvm/build/bin/clang > LLC ?= llc > CLANG ?= clang > OPT ?= opt >diff --git a/samples/bpf/README.rst b/samples/bpf/README.rst >index dd34b2d..d1be438 100644 >--- a/samples/bpf/README.rst >+++ b/samples/bpf/README.rst >@@ -65,17 +65,20 @@ To generate a smaller llc binary one can use:: > Quick sniplet for manually compiling LLVM and clang > (build dependencies are cmake and gcc-c++):: > >- $ git clone http://llvm.org/git/llvm.git >- $ cd llvm/tools >- $ git clone --depth 1 http://llvm.org/git/clang.git >- $ cd ..; mkdir build; cd build >- $ cmake .. -DLLVM_TARGETS_TO_BUILD="BPF;X86" >- $ make -j $(getconf _NPROCESSORS_ONLN) >+ $ git clone https://github.com/llvm/llvm-project.git >+ $ mkdir -p llvm-project/llvm/build/install llvm-project/llvm/build/install is not used. >+ $ cd llvm-project/llvm/build >+ $ cmake .. -G "Ninja" -DLLVM_TARGETS_TO_BUILD="BPF;X86" \ >+ -DLLVM_ENABLE_PROJECTS="clang" \ >+ -DBUILD_SHARED_LIBS=OFF \ -DBUILD_SHARED_LIBS=OFF is the default. It can be omitted. >+ -DCMAKE_BUILD_TYPE=Release \ >+ -DLLVM_BUILD_RUNTIME=OFF -DLLVM_BUILD_RUNTIME=OFF can be omitted if none of compiler-rt/libc++/libc++abi is built. >+ $ ninja > > It is also possible to point make to the newly compiled 'llc' or > 'clang' command via redefining LLC or CLANG on the make command line:: > >- make M=samples/bpf LLC=~/git/llvm/build/bin/llc CLANG=~/git/llvm/build/bin/clang >+ make M=samples/bpf LLC=~/git/llvm-project/llvm/build/bin/llc CLANG=~/git/llvm-project/llvm/build/bin/clang > > Cross compiling samples > ----------------------- >-- >2.1.0 > >-- >You received this message because you are subscribed to the Google Groups "Clang Built Linux" group. >To unsubscribe from this group and stop receiving emails from it, send an email to clang-built-linux+unsubscribe@googlegroups.com. >To view this discussion on the web visit https://groups.google.com/d/msgid/clang-built-linux/1611042978-21473-1-git-send-email-yangtiezhu%40loongson.cn.