DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: FreeBSD 14.0 build failure
Date: Thu, 18 Jan 2024 09:35:16 +0000	[thread overview]
Message-ID: <Zajw1PHpQBXfLju_@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20240117182811.485e8be7@hermes.local>

On Wed, Jan 17, 2024 at 06:28:11PM -0800, Stephen Hemminger wrote:
> DPDK will not build on FreeBSD 14.0
> 
> [2/2] Generating kernel/freebsd/nic_uio with a custom command
> FAILED: kernel/freebsd/nic_uio.ko 
> /usr/bin/make -f ../kernel/freebsd/BSDmakefile.meson KMOD_OBJDIR=kernel/freebsd KMOD_SRC=../kernel/freebsd/nic_uio/nic_uio.c KMOD=nic_uio 'KMOD_CFLAGS=-I/home/shemminger/dpdk/build -I/home/shemminger/dpdk/config -include rte_config.h' CC=clang
> clang  -O2 -pipe -include rte_config.h  -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc  -I/home/shemminger/dpdk/build -I/home/shemminger/dpdk/config -include /home/shemminger/dpdk/build/kernel/freebsd/opt_global.h -I. -I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno-common  -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fdebug-prefix-map=./machine=/usr/src/sys/amd64/include -fdebug-prefix-map=./x86=/usr/src/sys/x86/include -fdebug-prefix-map=./i386=/usr/src/sys/i386/include     -MD  -MF.depend.nic_uio.o -MTnic_uio.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error=tautological-compare -Wno-error=empty-body -Wno-error=parentheses-equality -Wno-error=unused-function -Wno-error=pointer-sign -Wno-error=shift-negative-value -Wno-address-of-packed-member -Wno-format-zero-length   -mno-aes -mno-avx  -std=gnu99 -c /home/shemminger/dpdk/kernel/freebsd/nic_uio/nic_uio.c -o nic_uio.o
> /home/shemminger/dpdk/kernel/freebsd/nic_uio/nic_uio.c:84:81: error: too many arguments provided to function-like macro invocation
> DRIVER_MODULE(nic_uio, pci, nic_uio_driver, nic_uio_devclass, nic_uio_modevent, 0);
>                                                                                 ^
> /usr/src/sys/sys/bus.h:832:9: note: macro 'DRIVER_MODULE' defined here
> #define DRIVER_MODULE(name, busname, driver, evh, arg)                  \
>         ^
> /home/shemminger/dpdk/kernel/freebsd/nic_uio/nic_uio.c:84:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Werror,-Wimplicit-int]
> DRIVER_MODULE(nic_uio, pci, nic_uio_driver, nic_uio_devclass, nic_uio_modevent, 0);
> ^

Yes. I've sent out a patch last month for this:

https://patches.dpdk.org/project/dpdk/patch/20231219112959.10440-1-bruce.richardson@intel.com/

/Bruce

      reply	other threads:[~2024-01-18  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  2:28 Stephen Hemminger
2024-01-18  9:35 ` Bruce Richardson [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 \
    --in-reply-to=Zajw1PHpQBXfLju_@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).