From: Peter Korsgaard <peter@korsgaard.com>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/hostapd: fix static build issue with zlib-ng
Date: Sun, 13 Nov 2022 17:47:59 +0100 [thread overview]
Message-ID: <87o7taol6o.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220916210059.2395129-2-geomatsi@gmail.com> (Sergey Matyukevich's message of "Sat, 17 Sep 2022 00:00:58 +0300")
>>>>> "Sergey" == Sergey Matyukevich <geomatsi@gmail.com> writes:
> Hostapd uses 'crc32' name for IEEE802.11 CRC-32 routine. This name is
> too generic. Buildroot autobuilder detected configurations that failed
> to build due to the naming conflict with zlib-ng.
> Add hostapd part of the upstream patch that renames 'crc32' function
> to a less generic 'ieee80211_crc32' name.
> Fixes: http://autobuild.buildroot.net/results/9901df820d3afa4cde78e8ad6d62cb8ce7e69fdb/
> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
Committed to 2022.08.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-13 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 21:00 [Buildroot] [PATCH v2 0/2] hostapd/wpa_s: fix static build issue with zlib-ng Sergey Matyukevich
2022-09-16 21:00 ` [Buildroot] [PATCH v2 1/2] package/hostapd: " Sergey Matyukevich
2022-11-13 16:47 ` Peter Korsgaard [this message]
2022-09-16 21:00 ` [Buildroot] [PATCH v2 2/2] package/wpa_supplicant: " Sergey Matyukevich
2022-11-13 16:48 ` Peter Korsgaard
2022-10-31 12:19 ` [Buildroot] [PATCH v2 0/2] hostapd/wpa_s: " Thomas Petazzoni via buildroot
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=87o7taol6o.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=matthew.weber@collins.com \
--cc=thomas.petazzoni@bootlin.com \
/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