Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinktrace: disable on arm*, enable on aarch64*
Date: Tue, 24 Aug 2021 20:22:30 +0200	[thread overview]
Message-ID: <20210824182230.2ONxUP9YoyTIGMxnUHUuf1dkzXZbcxF7CetFdnzhg8A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32654@inbox.vuxu.org>

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

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/32654#issuecomment-904871931

Comment:
> Wait, isn't it working correctly on aarch64?

```
syscall-special.c:62:3: warning: #warning is a GCC extension
   62 | # warning do not know the size of stat buffer for non-default ABIs
      |   ^~~~~~~
syscall-special.c:62:3: warning: #warning do not know the size of stat buffer for non-default ABIs [-Wcpp]
  CC       sydbox-syscall-filter.o
  CC       sydbox-syscall.o
syscall.c: In function 'seccomp_apply':
syscall.c:484:7: error: 'PINK_ABI_X86_64' undeclared (first use in this function); did you mean 'PINK_ARCH_X86_64'?
  484 |  case PINK_ABI_X86_64:
      |       ^~~~~~~~~~~~~~~
      |       PINK_ARCH_X86_64
syscall.c:484:7: note: each undeclared identifier is reported only once for each function it appears in
syscall.c:487:7: error: 'PINK_ABI_I386' undeclared (first use in this function); did you mean 'PINK_ARCH_I386'?
  487 |  case PINK_ABI_I386:
      |       ^~~~~~~~~~~~~
      |       PINK_ARCH_I386
syscall.c: In function 'sysinit_seccomp':
syscall.c:702:2: error: #error "Platform does not support seccomp filter yet"
  702 | #error "Platform does not support seccomp filter yet"
      |  ^~~~~
syscall.c:671:9: warning: unused variable 'i' [-Wunused-variable]
  671 |  size_t i;
      |         ^
At top level:
syscall.c:453:12: warning: 'apply_simple_filter' defined but not used [-Wunused-function]
  453 | static int apply_simple_filter(const sysentry_t *entry, int arch, int abi)
      |            ^~~~~~~~~~~~~~~~~~~
```

Would you line to take this PR? You know a lot more about these packages than I do. Feel free to push here.

  parent reply	other threads:[~2021-08-24 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 17:55 [PR PATCH] " paper42
2021-08-24 17:58 ` paper42
2021-08-24 18:15 ` [PR PATCH] [Updated] " paper42
2021-08-24 18:16 ` thypon
2021-08-24 18:22 ` paper42 [this message]
2021-08-24 18:24 ` thypon
2021-08-24 18:26 ` paper42
2021-08-24 18:40 ` q66
2021-08-24 18:40 ` [PR PATCH] [Closed]: " q66

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=20210824182230.2ONxUP9YoyTIGMxnUHUuf1dkzXZbcxF7CetFdnzhg8A@z \
    --to=paper42@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).