Github messages for voidlinux
 help / color / mirror / Atom feed
From: sbogomolov <sbogomolov@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: interception-tools-0.6.6, caps2esc-0.3.2
Date: Mon, 12 Jul 2021 23:11:28 +0200	[thread overview]
Message-ID: <20210712211128.pxu6nEC7qnOpl9RXe34saH0kawilIuCrMJrGmjE8Ttk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31575@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 510 bytes --]

New comment by sbogomolov on void-packages repository

https://github.com/void-linux/void-packages/pull/31575#issuecomment-878595117

Comment:
Another merge request to replace `__pid_t` with `pid_t`: https://gitlab.com/interception/linux/tools/-/merge_requests/17.
This allows to build it with `musl`. I'll add a patch for that as well (until it gets merged and new version is released).

These two patches should fix all the builds. At lest "it works on my machine" (as in builds for all architectures) :)

  parent reply	other threads:[~2021-07-12 21:11 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31575@inbox.vuxu.org>
2021-06-28 22:00 ` sbogomolov
2021-06-28 22:01 ` sbogomolov
2021-07-10 21:55 ` sbogomolov
2021-07-11  3:15 ` ericonr
2021-07-11  3:16 ` [PR REVIEW] " ericonr
2021-07-11  3:18 ` ericonr
2021-07-11  3:18 ` ericonr
2021-07-11 21:30 ` sbogomolov
2021-07-11 21:30 ` [PR REVIEW] " sbogomolov
2021-07-11 21:31 ` sbogomolov
2021-07-11 21:31 ` sbogomolov
2021-07-11 21:55 ` sbogomolov
2021-07-11 21:57 ` [PR PATCH] [Updated] " sbogomolov
2021-07-11 22:01 ` sbogomolov
2021-07-11 22:23 ` [PR REVIEW] " ericonr
2021-07-11 22:25 ` ericonr
2021-07-12 19:37 ` sbogomolov
2021-07-12 19:46 ` ericonr
2021-07-12 20:45 ` sbogomolov
2021-07-12 21:06 ` sbogomolov
2021-07-12 21:06 ` sbogomolov
2021-07-12 21:11 ` sbogomolov [this message]
2021-07-12 21:13 ` [PR PATCH] [Updated] " sbogomolov
2021-07-12 21:18 ` [PR REVIEW] " sbogomolov
2021-07-12 21:28 ` ericonr
2021-07-12 21:32 ` [PR PATCH] [Updated] " sbogomolov
2021-07-12 21:32 ` [PR REVIEW] " sbogomolov
2021-07-13 10:43 ` sbogomolov
2021-07-13 13:46 ` [PR PATCH] [Updated] " sbogomolov
2021-07-14 13:41 ` ericonr
2021-07-14 13:47 ` sbogomolov
2021-07-14 13:48 ` sbogomolov
2021-07-14 13:48 ` sbogomolov
2021-07-15 18:25 ` [PR PATCH] [Updated] " sbogomolov
2021-07-15 18:26 ` New packages: interception-tools-0.6.7, caps2esc-0.3.2 sbogomolov
2021-07-15 21:08 ` [PR REVIEW] " paper42
2021-07-15 21:25 ` sbogomolov
2021-07-15 21:26 ` sbogomolov
2021-07-15 21:28 ` [PR PATCH] [Updated] " sbogomolov
2021-07-17  3:04 ` [PR REVIEW] " ericonr
2021-07-17  3:04 ` ericonr
2021-07-17  3:04 ` ericonr
2021-07-17  8:27 ` sbogomolov
2021-07-17  8:40 ` sbogomolov
2021-07-17  8:40 ` sbogomolov
2021-07-17  8:43 ` [PR PATCH] [Updated] " sbogomolov
2021-07-17  9:00 ` sbogomolov
2021-07-20 19:02 ` sbogomolov
2021-07-20 21:11 ` [PR PATCH] [Merged]: " 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=20210712211128.pxu6nEC7qnOpl9RXe34saH0kawilIuCrMJrGmjE8Ttk@z \
    --to=sbogomolov@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).