From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: lshw: clean up musl patches.
Date: Tue, 12 Jan 2021 04:04:53 +0100 [thread overview]
Message-ID: <20210112030453.OTtFFtgwwWTMyF9CvchmLA_xaXPQfqp_3PXeDXNTW6I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27826@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
There's a merged pull request on the void-packages repository
lshw: clean up musl patches.
https://github.com/void-linux/void-packages/pull/27826
Description:
musl-path_max was no longer necessary, and musl-confname_h was kind of
helping them do the wrong thing. They should just be using the value of
LONG_BIT instead of trying to pass it to sysconf, so the usage was wrong
on glibc and musl. _SC_LONG_BIT is a glibc extension and shouldn't be at
all needed.
Since this does change behavior (sysconf(LONG_BIT) could return
arbitrary values), revbump the package.
prev parent reply other threads:[~2021-01-12 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:04 [PR PATCH] " ericonr
2021-01-12 3:04 ` ericonr [this message]
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=20210112030453.OTtFFtgwwWTMyF9CvchmLA_xaXPQfqp_3PXeDXNTW6I@z \
--to=ericonr@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).