From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] broadcom-wl-dkms fails to build from source
Date: Thu, 13 Jan 2022 07:47:26 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35024@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
New issue by unspecd on void-packages repository
https://github.com/void-linux/void-packages/issues/35024
Description:
<!-- Don't request update of package. We have a script for that. httqinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*Void 5.15.14_1 x86_64-musl GenuineIntel uptodate rFFFF*
* package:
*broadcom-wl-dkms-6.30.223.271_11*
### Actual behavior
```
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> broadcom-wl-dkms-6.30.223.271_11: running do-fetch hook: 00-distfiles ...
=> broadcom-wl-dkms-6.30.223.271_11: running do-extract hook: 00-distfiles ...
=> broadcom-wl-dkms-6.30.223.271_11: extracting distfile(s), please wait...
=> broadcom-wl-dkms-6.30.223.271_11: running do-patch hook: 00-patches ...
=> broadcom-wl-dkms-6.30.223.271_11: patching: 001-null-pointer-fix.patch.
=> broadcom-wl-dkms-6.30.223.271_11: patching: gcc-4.9.patch.
=> broadcom-wl-dkms-6.30.223.271_11: patching: linux-4.11.patch.
=> broadcom-wl-dkms-6.30.223.271_11: patching: linux-4.12.patch.
=> broadcom-wl-dkms-6.30.223.271_11: patching: linux-4.15.patch.
3 out of 3 hunks FAILED -- saving rejects to file src/wl/sys/wl_linux.c.rej
=> ERROR: broadcom-wl-dkms-6.30.223.271_11: do-patch_00-patches: 'patch -s ${_args} -i ${_patch} 2> /dev/null' exited with 1
=> ERROR: in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR: in hook() at common/hooks/do-patch/00-patches.sh:51
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:245
=> ERROR: in run_step() at common/xbps-src/shutils/common.sh:71
=> ERROR: in main() at common/xbps-src/libexec/xbps-src-dopatch.sh:33
```
### Steps to reproduce the behavior
```shell
$ ./xbps-src -NI patch broadcom-wl-dkms
```
git bisect identifies 7b4119df5cbc0cc37348164a10c88a32910009d8 as the bad commit.
next reply other threads:[~2022-01-13 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 6:47 unspecd [this message]
2022-01-16 20:58 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35024@inbox.vuxu.org \
--to=unspecd@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).