From: James Prestwood <prestwoj@gmail.com>
To: Martin Petzold <martin.petzold@tavla.de>
Cc: "iwd@lists.linux.dev" <iwd@lists.linux.dev>,
Denis Kenzior <denkenz@gmail.com>
Subject: Re: IWD 1.27 with brcmfmac not working for roaming
Date: Thu, 10 Oct 2024 06:55:04 -0700 [thread overview]
Message-ID: <b6f570d9-c14d-4e71-87a7-3e7d2c2fd6ca@gmail.com> (raw)
In-Reply-To: <1fcf76fd-85ab-4a31-8aaf-9d6922ab3a97@tavla.de>
Hi Martin,
On 10/10/24 6:47 AM, Martin Petzold wrote:
> Hi James,
>
> Am 10.10.24 um 15:36 schrieb James Prestwood:
>>
>> On 10/10/24 6:20 AM, Martin Petzold wrote:
>>> Hi Denis,
>>>
>>> Am 09.10.24 um 18:07 schrieb Denis Kenzior:
>>>> [...]
>>>>
>>>>> 3. Build IWD 2.22 from source (maybe using Debian sid source
>>>>> package?) -> how to do best and will this work with libc6 version
>>>>> 2.36? Missing libreadline8t64?
>>>>
>>>> I mean this is your only real solution. There is no 'long term
>>>> support' model for iwd. You either run the latest or you're on
>>>> your own. It is highly unlikely that any of the developers will
>>>> look at logs (or attempt to fix) anything but the latest version.
>>>>
>>>>
>>> Why does the following build fail. I did not install
>>> 'python-docutils' package because is is not available for Debian
>>> bookworm (only a source package). How should I proceed? Maybe the
>>> documentation should be fixed then for Debian bookworm.
>> You need to use an updated version of ELL. IWD and ELL get released
>> in tandem in case of any API/behavior changes.
>
> I used for both git HEAD repository (how can I get both in line?):
Sorry, I just glanced over the error and assumed incorrectly. It looks
like -Werror isn't enabled (?) so that warning should be fine. But the
issue, as you said, is docs related. You could try to configure with
--disable-manual-pages
> src/eap.c: In function ‘eap_rx_packet’:
> src/eap.c:419:57: warning: ‘vendor_type’ may be used uninitialized
> [-Wmaybe-uninitialized]
> 419 | (type == EAP_TYPE_EXPANDED && vendor_id == (id) &&
> vendor_type == (t))
> | ^~
> src/eap.c:429:18: note: ‘vendor_type’ was declared here
> 429 | uint32_t vendor_type;
> | ^~~~~~~~~~~
> src/eap.c:419:49: warning: ‘vendor_id’ may be used uninitialized
> [-Wmaybe-uninitialized]
> 419 | (type == EAP_TYPE_EXPANDED && vendor_id == (id) &&
> vendor_type == (t))
> | ^~
> src/eap.c:428:18: note: ‘vendor_id’ was declared here
> 428 | uint32_t vendor_id;
> | ^~~~~~~~~
> CC src/eap-md5.o
> CC src/eap-tls.o
> CC src/eap-ttls.o
> CC src/eap-mschapv2.o
> CC src/eap-sim.o
> CC src/eap-aka.o
> CC src/eap-peap.o
> CC src/eap-gtc.o
> CC src/eap-pwd.o
> CC src/simutil.o
> CC src/simauth.o
> CC src/eap-tls-common.o
> CC src/mschaputil.o
> CCLD src/iwd
> CC tools/probe-req.o
> CCLD tools/probe-req
> CC tools/iwd-decrypt-profile.o
> CCLD tools/iwd-decrypt-profile
> GEN src/iwd.8
> Generated manual page src/iwd.8 does not exist
> make[1]: *** [Makefile:4106: src/iwd.8] Fehler 1
> make: *** [Makefile:1746: all] Fehler 2
>
next prev parent reply other threads:[~2024-10-10 13:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:43 IWD 1.27 with brcmfmac not working for roaming Martin Petzold
2024-10-09 16:07 ` Denis Kenzior
2024-10-09 16:50 ` Arend Van Spriel
2024-10-09 17:54 ` Martin Petzold
2024-10-10 8:06 ` Martin Petzold
2024-10-12 11:06 ` Martin Petzold
2024-10-12 11:51 ` Arend van Spriel
2024-10-13 15:43 ` Martin Petzold
2024-10-30 19:19 ` Martin Petzold
2024-10-30 19:23 ` James Prestwood
2024-10-09 16:58 ` Arend Van Spriel
2024-10-10 13:20 ` Martin Petzold
2024-10-10 13:36 ` James Prestwood
2024-10-10 13:47 ` Martin Petzold
2024-10-10 13:55 ` James Prestwood [this message]
2024-10-11 8:35 ` Martin Petzold
2024-10-11 10:46 ` Martin Petzold
2024-10-12 10:59 ` Martin Petzold
2024-10-15 14:43 ` Martin Petzold
2024-10-15 15:17 ` Denis Kenzior
2024-10-15 19:13 ` Arend van Spriel
2024-10-16 2:04 ` Denis Kenzior
2024-10-16 8:32 ` Arend van Spriel
2024-10-17 10:58 ` Martin Petzold
2024-10-19 14:04 ` Martin Petzold
2024-10-19 14:41 ` Denis Kenzior
2024-10-21 13:34 ` Martin Petzold
2024-10-21 14:40 ` Arend Van Spriel
2024-10-21 14:53 ` Martin Petzold
2024-10-21 15:23 ` James Prestwood
2024-10-21 17:08 ` Arend Van Spriel
2024-10-21 17:20 ` Martin Petzold
2024-10-21 17:40 ` Denis Kenzior
2024-10-21 18:26 ` Arend van Spriel
2024-10-21 18:45 ` Martin Petzold
2024-10-21 18:48 ` Martin Petzold
2024-10-21 18:55 ` Denis Kenzior
2024-10-21 19:08 ` Jeremy Blum
2024-10-22 15:26 ` Denis Kenzior
2024-10-22 16:38 ` Jeremy Blum
2024-10-21 19:15 ` Martin Petzold
2024-10-21 19:11 ` James Prestwood
2024-10-21 20:23 ` Martin Petzold
2024-10-22 6:08 ` Arend Van Spriel
2024-10-21 22:01 ` KeithG
2024-10-21 22:10 ` Martin Petzold
2024-10-22 17:40 ` James Prestwood
2024-10-22 18:04 ` Martin Petzold
2024-10-22 18:21 ` Martin Petzold
2024-10-22 18:24 ` James Prestwood
2024-10-22 18:32 ` Martin Petzold
2024-10-22 18:44 ` Denis Kenzior
2024-10-22 18:47 ` Martin Petzold
2024-10-22 19:10 ` James Prestwood
2024-10-22 18:47 ` James Prestwood
2024-10-22 18:49 ` Martin Petzold
2024-10-22 18:52 ` Denis Kenzior
2024-10-23 12:02 ` Martin Petzold
2024-10-23 12:13 ` James Prestwood
2024-10-23 12:19 ` Martin Petzold
2024-10-23 13:22 ` James Prestwood
2024-10-23 13:34 ` Martin Petzold
2024-10-23 15:22 ` Martin Petzold
2024-10-23 15:27 ` Martin Petzold
2024-10-23 15:30 ` James Prestwood
2024-10-23 15:37 ` Martin Petzold
2024-10-23 15:28 ` James Prestwood
2024-10-23 15:11 ` Arend Van Spriel
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=b6f570d9-c14d-4e71-87a7-3e7d2c2fd6ca@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=martin.petzold@tavla.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.