From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Pavel Begunkov <asml.silence@gmail.com>,
Gilang Fachrezy <gilang4321@gmail.com>,
VNLX Kernel Department <kernel@vnlx.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
io-uring Mailing List <io-uring@vger.kernel.org>
Subject: [RFC PATCH liburing v1 1/2] github: Remove nolibc build on the GitHub CI bot
Date: Fri, 6 Jan 2023 22:52:01 +0700 [thread overview]
Message-ID: <20230106155202.558533-2-ammar.faizi@intel.com> (raw)
In-Reply-To: <20230106155202.558533-1-ammar.faizi@intel.com>
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
This is a preparation patch to deprecate `--nolibc` configure option.
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
.github/workflows/build.yml | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index c2aa3e6..f18f069 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -117,16 +117,6 @@ jobs:
./configure --cc=${{matrix.cc}} --cxx=${{matrix.cxx}};
make -j$(nproc) V=1 CPPFLAGS="-Werror" CFLAGS="$FLAGS" CXXFLAGS="$FLAGS";
- - name: Build nolibc
- run: |
- if [[ "${{matrix.arch}}" == "x86_64" || "${{matrix.arch}}" == "i686" || "${{matrix.arch}}" == "aarch64" ]]; then \
- make clean; \
- ./configure --cc=${{matrix.cc}} --cxx=${{matrix.cxx}} --nolibc; \
- make -j$(nproc) V=1 CPPFLAGS="-Werror" CFLAGS="$FLAGS" CXXFLAGS="$FLAGS"; \
- else \
- echo "Skipping nolibc build, this arch doesn't support building liburing without libc"; \
- fi;
-
- name: Test install command
run: |
sudo make install;
--
Ammar Faizi
next prev parent reply other threads:[~2023-01-06 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 15:52 [RFC PATCH liburing v1 0/2] Always enable CONFIG_NOLIBC if supported and deprecate --nolibc option Ammar Faizi
2023-01-06 15:52 ` Ammar Faizi [this message]
2023-01-06 15:52 ` [RFC PATCH liburing v1 2/2] configure: Always enable `CONFIG_NOLIBC` if the arch is supported Ammar Faizi
2023-01-06 22:39 ` [RFC PATCH liburing v1 0/2] Always enable CONFIG_NOLIBC if supported and deprecate --nolibc option Jens Axboe
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=20230106155202.558533-2-ammar.faizi@intel.com \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gilang4321@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=kernel@vnlx.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox