public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>,
	Pavel Begunkov <[email protected]>,
	io-uring Mailing List <[email protected]>
Cc: Bedirhan KURT <[email protected]>,
	Louvian Lyndal <[email protected]>
Subject: Re: [PATCH v2 liburing 4/4] Add CONFIG_NOLIBC variable and macro
Date: Sun, 10 Oct 2021 05:22:21 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 10/10/21 12:39 AM, Ammar Faizi wrote:
> For conditonal variable and macro to enable nolibc build.
> Add `--nolibc` option for `configure` to enable it.
> 
> Link: https://github.com/axboe/liburing/issues/443
> Signed-off-by: Ammar Faizi <[email protected]>
> ---
>  configure    |  8 ++++++++
>  src/Makefile | 13 ++++++++++++-
>  2 files changed, 20 insertions(+), 1 deletion(-)
> 
> diff --git a/configure b/configure
> index 92f51bd..6712ce3 100755
> --- a/configure
> +++ b/configure
> @@ -24,6 +24,8 @@ for opt do
>    ;;
>    --cxx=*) cxx="$optarg"
>    ;;
> +  --nolibc) liburing_nolibc="yes"
> +  ;;
>    *)
>      echo "ERROR: unknown option $opt"
>      echo "Try '$0 --help' for more information"

This also needs an addition in the configure --help section.

> diff --git a/src/Makefile b/src/Makefile
> index 5e46a9d..290517d 100644
> --- a/src/Makefile
> +++ b/src/Makefile
> @@ -32,11 +32,22 @@ endif
>  
>  all: $(all_targets)
>  
> -liburing_srcs := setup.c queue.c syscall.c register.c
> +liburing_srcs := setup.c queue.c register.c
> +
> +ifeq ($(CONFIG_NOLIBC),y)
> +	liburing_srcs += nolibc.c
> +	override CFLAGS += -nostdlib -nolibc -nodefaultlibs -ffreestanding -fno-stack-protector
> +	override CPPFLAGS += -nostdlib -nolibc -nodefaultlibs -ffreestanding -fno-stack-protector
> +	override LINK_FLAGS += -nostdlib -nolibc -nodefaultlibs
> +else
> +	liburing_srcs += syscall.c
> +endif

If I build this with clang, I get a lot of:

clang: warning: argument unused during compilation: '-nolibc' [-Wunused-command-line-argument]

Apart from this reply and the little language tweaks I suggested, I
think this now looks good. If you can respin with these things fixed,
let's get it applied.

-- 
Jens Axboe


      reply	other threads:[~2021-10-10 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10  6:39 [PATCHSET v2 liburing 0/4] Add nolibc support for x86-64 arch Ammar Faizi
2021-10-10  6:39 ` [PATCH v2 liburing 1/4] test/thread-exit: Fix use after free bug Ammar Faizi
2021-10-10 11:25   ` Jens Axboe
2021-10-10  6:39 ` [PATCH v2 liburing 2/4] Add arch dependent directory and files Ammar Faizi
2021-10-10 11:16   ` Jens Axboe
2021-10-10  6:39 ` [PATCH v2 liburing 3/4] Add no libc build support Ammar Faizi
2021-10-10 11:19   ` Jens Axboe
2021-10-10  6:39 ` [PATCH v2 liburing 4/4] Add CONFIG_NOLIBC variable and macro Ammar Faizi
2021-10-10 11:22   ` Jens Axboe [this message]

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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