From: Grant Erickson <gerickson@nuovations.com>
To: iwd@lists.linux.dev
Cc: Marcel Holtmann <marcel@holtmann.org>, Denis Kenzior <denkenz@gmail.com>
Subject: IWD 2.9 Does Not Compile against Linux-4.9.212 and/or GLibC-2.28
Date: Sun, 26 Nov 2023 14:21:35 -0800 [thread overview]
Message-ID: <29B7EAE3-2BBD-43CA-B2E7-28CE588EE7A2@nuovations.com> (raw)
IWD Community:
Over on the connman and ell mailing lists, Marcel and Denis have been advocating, rightly so, for iwd over wpa_supplicant for Wi-Fi.
Is there a kernel version expectation of IWD?
For the current project I am engaged on, the kernel is locked at linux-4.9.212, glibc-2.28, and GCC 8.2. With that combination, I have found any reasonably modern version of IWD fails to build.
Denis and Marcel expediently put in place a few patches to make ell-0.61 compile. I suspect a similar set of patches for ell are also applicable to iwd:
make[1]: Entering directory '${BuildRoot}/third_party/iwd/.build/Makefile/${PRODUCT}/arm/gnu-toolchain/12.3.1/release'
GEN ell/shared
GEN src/builtin.h
make --no-print-directory all-am
CC client/main.o
CC client/adapter.o
CC client/agent.o
CC client/agent-manager.o
CC client/ad-hoc.o
CC client/ap.o
CC client/command.o
CC client/dbus-proxy.o
CC client/device.o
CC client/display.o
CC client/known-networks.o
${BuildRoot}/third_party/iwd/iwd-2.9/client/known-networks.c:27: warning: "_XOPEN_SOURCE" redefined
27 | #define _XOPEN_SOURCE
|
<command-line>: note: this is the location of the previous definition
${BuildRoot}/third_party/iwd/iwd-2.9/client/display.c: In function ‘display_init’:
${BuildRoot}/third_party/iwd/iwd-2.9/client/display.c:949:44: warning: assignment to ‘void (*)(void)’ from incompatible pointer type ‘void (*)(char **, int, int)’ [-Wincompatible-pointer-types]
949 | rl_completion_display_matches_hook = display_completion_matches;
| ^
CC client/network.o
CC client/properties.o
CC client/wsc.o
CC client/station.o
CC client/diagnostic.o
CC client/daemon.o
CC client/dpp.o
CC client/dpp-pkex.o
CC client/station-debug.o
CC src/util.o
CC src/band.o
CC monitor/main.o
CC monitor/nlmon.o
CC monitor/pcap.o
CC monitor/display.o
CC src/ie.o
CC src/wscutil.o
CC src/mpdu.o
CC src/crypto.o
CC src/watchlist.o
CC src/eapolutil.o
CC src/nl80211cmd.o
CC src/p2putil.o
CC src/anqputil.o
CC src/main.o
CC src/netdev.o
CC src/wiphy.o
CC src/device.o
CC src/station.o
CC src/dbus.o
CC src/eapol.o
CC src/handshake.o
CC src/scan.o
CC src/common.o
CC src/agent.o
CC src/storage.o
CC src/network.o
CC src/wsc.o
CC src/backtrace.o
CC src/knownnetworks.o
CC src/rfkill.o
CC src/ft.o
CC src/ap.o
CC src/adhoc.o
CC src/sae.o
In file included from ${BuildRoot}/third_party/iwd/iwd-2.9/src/adhoc.c:28:
${BuildRoot}/results/${PRODUCT}/arm/gnu-toolchain/12.3.1/release/third_party/linux/linux-dey/include/linux/if.h:234:34: error: field ‘ifru_addr’ has incomplete type
234 | struct sockaddr ifru_addr;
| ^~~~~~~~~
${BuildRoot}/results/${PRODUCT}/arm/gnu-toolchain/12.3.1/release/third_party/linux/linux-dey/include/linux/if.h:235:34: error: field ‘ifru_dstaddr’ has incomplete type
235 | struct sockaddr ifru_dstaddr;
| ^~~~~~~~~~~~
${BuildRoot}/results/${PRODUCT}/arm/gnu-toolchain/12.3.1/release/third_party/linux/linux-dey/include/linux/if.h:236:34: error: field ‘ifru_broadaddr’ has incomplete type
236 | struct sockaddr ifru_broadaddr;
| ^~~~~~~~~~~~~~
${BuildRoot}/results/${PRODUCT}/arm/gnu-toolchain/12.3.1/release/third_party/linux/linux-dey/include/linux/if.h:237:34: error: field ‘ifru_netmask’ has incomplete type
237 | struct sockaddr ifru_netmask;
| ^~~~~~~~~~~~
${BuildRoot}/results/${PRODUCT}/arm/gnu-toolchain/12.3.1/release/third_party/linux/linux-dey/include/linux/if.h:238:34: error: field ‘ifru_hwaddr’ has incomplete type
238 | struct sockaddr ifru_hwaddr;
| ^~~~~~~~~~~
make[2]: *** [Makefile:2539: src/adhoc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1713: all] Error 2
make[1]: Leaving directory '${BuildRoot}/third_party/iwd/.build/Makefile/${PRODUCT}/arm/gnu-toolchain/12.3.1/release'
make: *** [Makefile:110: build] Error 2
I expect the ’sockaddr’ issues to be easily resolved with a different set of include directives; however, the rest appear to be new symbols introduced in later kernels.
Best,
Grant
next reply other threads:[~2023-11-26 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 22:21 Grant Erickson [this message]
2023-11-27 3:25 ` IWD 2.9 Does Not Compile against Linux-4.9.212 and/or GLibC-2.28 Denis Kenzior
2023-11-27 10:25 ` Marcel Holtmann
2023-11-27 20:35 ` Grant Erickson
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=29B7EAE3-2BBD-43CA-B2E7-28CE588EE7A2@nuovations.com \
--to=gerickson@nuovations.com \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=marcel@holtmann.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 read-only IMAP folder(s) and NNTP newsgroup(s).