From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libserialport: add patch to prevent it from using termiox, which has been removed from recent kernels
Date: Mon, 19 Jul 2021 22:26:31 +0200 [thread overview]
Message-ID: <20210719202631._frkznFYs-0T2zQJ5oB_fndJ6soTLe1eztr2M6INdWE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32025@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
There's a merged pull request on the void-packages repository
libserialport: add patch to prevent it from using termiox, which has been removed from recent kernels
https://github.com/void-linux/void-packages/pull/32025
Description:
Without this patch, libserialport will fail opening a tty device with an "No such ioctl for device"-error. This prevents eg. sigrok/pulseview from working with a SUMP-compatible logic analyzer.
EDIT: some clarification: [see here](https://sigrok.org/gitweb/?p=libserialport.git;a=commit;h=6f9b03e597ea7200eb616a4e410add3dd1690cb1), something like their patches would work better, but, honestly, libserialport should have a new release, 0.1.1 is from years ago.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
prev parent reply other threads:[~2021-07-19 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 20:16 [PR PATCH] add patch to prevent libserialport " PoroCYon
2021-07-17 20:19 ` [PR PATCH] [Updated] " PoroCYon
2021-07-17 20:20 ` PoroCYon
2021-07-17 20:22 ` PoroCYon
2021-07-17 21:18 ` libserialport: add patch to prevent it " ericonr
2021-07-17 21:29 ` lemmi
2021-07-17 21:35 ` PoroCYon
2021-07-17 21:38 ` PoroCYon
2021-07-17 21:41 ` lemmi
2021-07-17 21:43 ` [PR PATCH] [Updated] " PoroCYon
2021-07-17 21:44 ` PoroCYon
2021-07-17 21:52 ` lemmi
2021-07-19 20:26 ` lemmi [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=20210719202631._frkznFYs-0T2zQJ5oB_fndJ6soTLe1eztr2M6INdWE@z \
--to=lemmi@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).