Skip to content

Commit

Permalink
Merge pull request #2191 from nghttp2/bump-libbpf
Browse files Browse the repository at this point in the history
Bump libbpf to v1.4.2
  • Loading branch information
tatsuhiro-t committed May 13, 2024
2 parents dddb904 + c767d8a commit 40c54a6
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ on: [push, pull_request]
permissions: read-all

env:
LIBBPF_VERSION: v1.3.0
LIBBPF_VERSION: v1.4.2
OPENSSL1_VERSION: 1_1_1w+quic
OPENSSL3_VERSION: 3.1.5+quic
BORINGSSL_VERSION: 6ab7c1482bf4cdc91c87bc512aaf68ffb18975ec
Expand Down
4 changes: 2 additions & 2 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ Use ``--with-libbpf`` configure option to build eBPF program.
libelf-dev is needed to build libbpf.

For Ubuntu 20.04, you can build libbpf from `the source code
<https://github.com/libbpf/libbpf/releases/tag/v1.3.0>`_. nghttpx
<https://github.com/libbpf/libbpf/releases/tag/v1.4.2>`_. nghttpx
requires eBPF program for reloading its configuration and hot swapping
its executable.

Expand Down Expand Up @@ -381,7 +381,7 @@ from source:

.. code-block:: text
$ git clone --depth 1 -b v1.3.0 https://github.com/libbpf/libbpf
$ git clone --depth 1 -b v1.4.2 https://github.com/libbpf/libbpf
$ cd libbpf
$ PREFIX=$PWD/build make -C src install
$ cd ..
Expand Down
2 changes: 1 addition & 1 deletion docker/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ RUN git clone --recursive --depth 1 -b v1.5.0 https://github.com/ngtcp2/ngtcp2 &
cd .. && \
rm -rf ngtcp2

RUN git clone --depth 1 -b v1.3.0 https://github.com/libbpf/libbpf && \
RUN git clone --depth 1 -b v1.4.2 https://github.com/libbpf/libbpf && \
cd libbpf && \
PREFIX=/usr/local make -C src install && \
cd .. && \
Expand Down

0 comments on commit 40c54a6

Please sign in to comment.