From: vishal.gupta_1@philips.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] wpa-supplicant: fix sed expression
Date: Fri, 19 Dec 2025 05:56:55 -0800 [thread overview]
Message-ID: <250823.1766152615641090465@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj-xn-KQUFor=QFG_OBq0MF1tuBacUYyQJUDwF2gqnZA9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hi Alexander,
In the do_configure function current intention of implementation is to first delete it when we copying and then depending on the PACKAGECONFIG assign it with correct value.
As delete is failed because the line start with "#" we will have two CONFIG_TLS value in final ".config" file
one, at some where middle of the file
#CONFIG_TLS=openssl
second, depending on package config, at the end of file as it's an append operation.
CONFIG_TLS=openssl / gnutls
do_configure () {
${MAKE} -C wpa_supplicant clean
sed -e '/^#\?CONFIG_TLS=/d' <wpa_supplicant/defconfig >wpa_supplicant/.config
if ${@ bb.utils.contains('PACKAGECONFIG', 'openssl', 'true', 'false', d) }; then
echo 'CONFIG_TLS=openssl' >>wpa_supplicant/.config
elif ${@ bb.utils.contains('PACKAGECONFIG', 'gnutls', 'true', 'false', d) }; then
echo 'CONFIG_TLS=gnutls' >>wpa_supplicant/.config
sed -i -e 's/\(^CONFIG_DPP=\)/#\1/' \
-e 's/\(^CONFIG_EAP_PWD=\)/#\1/' \
-e 's/\(^CONFIG_SAE=\)/#\1/' wpa_supplicant/.config
fi
So with this change there will be only one "CONFIG_TLS=<value>" option.
[-- Attachment #2: Type: text/html, Size: 25810 bytes --]
next prev parent reply other threads:[~2025-12-19 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 12:49 [PATCH 1/1] wpa-supplicant: fix sed expression Vishal Gupta
2025-12-19 13:30 ` [OE-core] " Alexander Kanavin
2025-12-19 13:56 ` vishal.gupta_1 [this message]
2026-01-08 14:12 ` Paul Barker
2026-01-09 16:33 ` vishal.gupta_1
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=250823.1766152615641090465@lists.openembedded.org \
--to=vishal.gupta_1@philips.com \
--cc=openembedded-core@lists.openembedded.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