All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Subject: Re: [PATCH virtme-docker 2/3] upgrade to ubuntu 23.10
Date: Tue, 30 Jan 2024 08:50:19 +0800	[thread overview]
Message-ID: <ZbhHy6GPo4UcCKy0@t480> (raw)
In-Reply-To: <dc2e14b63fd7ec288e015124919c28c9470d5913.1706422466.git.geliang@kernel.org>

On Sun, Jan 28, 2024 at 02:16:02PM +0800, Geliang Tang wrote:
> There will be many build errors when comliling bpf selftests under
> Ubuntu 22.04. Upgrade to 23.10 to use the new versions of gcc, clang
> and LLVM.
> 
> Fix sparse build errors for llvm-16. This part alse be sent to sparse
> upstream. It can be dropped from this patch when accepted.

This part has been upstreamed, we can drop it now from this patch.

> 
> Signed-off-by: Geliang Tang <geliang@kernel.org>
> ---
>  Dockerfile | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/Dockerfile b/Dockerfile
> index cf8c692..cbc11f7 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -1,4 +1,4 @@
> -FROM ubuntu:22.04
> +FROM ubuntu:23.10
>  
>  LABEL name=mptcp-upstream-virtme-docker
>  
> @@ -71,6 +71,10 @@ ARG SPARSE_GIT_SHA="ce1a6720f69e6233ec9abd4e9aae5945e05fda41" # include a fix fo
>  RUN cd /opt && \
>  	git clone "${SPARSE_GIT_URL}" sparse && \
>  	cd "sparse" && \
> +		sed -i 's/LLVMConstGEP(/LLVMConstGEP2(type, /g' sparse-llvm.c && \
> +		sed -i 's/LLVMBuildInBoundsGEP(builder/LLVMBuildInBoundsGEP2(builder, type/g' sparse-llvm.c && \
> +		sed -i 's/LLVMBuildLoad(fn->builder/LLVMBuildLoad2(fn->builder, insn_symbol_type(insn)/g' sparse-llvm.c && \
> +		sed -i 's/LLVMBuildCall(fn->builder/LLVMBuildCall2(fn->builder, insn_symbol_type(insn)/g' sparse-llvm.c && \
>  		make -j"$(nproc)" -l"$(nproc)" && \
>  		make PREFIX=/usr install && \
>  		cd .. && \
> -- 
> 2.40.1

  reply	other threads:[~2024-01-30  0:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28  6:16 [PATCH virtme-docker 0/3] bpf: add bpftests support Geliang Tang
2024-01-28  6:16 ` [PATCH virtme-docker 1/3] change watchdog to device Geliang Tang
2024-01-28  6:16 ` [PATCH virtme-docker 2/3] upgrade to ubuntu 23.10 Geliang Tang
2024-01-30  0:50   ` Geliang Tang [this message]
2024-01-30 15:50     ` Matthieu Baerts
2024-01-31  9:00       ` Geliang Tang
2024-01-28  6:16 ` [PATCH virtme-docker 3/3] bpf: add bpftests support Geliang Tang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZbhHy6GPo4UcCKy0@t480 \
    --to=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.