From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: igt-gpu-tools: update to 1.24, fix musl
Date: Tue, 12 Nov 2019 10:26:04 +0100 [thread overview]
Message-ID: <20191112092604.IHu0qxMoRy4JMr0Qz11wK6_nLkBFO4Ewb1IOdikW2LA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16392@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/pull/16392#issuecomment-552808381
Comment:
Some warnings due to `musl.patch`:
```
[14/366] Compiling C object 'benchmarks/cb1d2fd@@gem_syslatency@exe/gem_syslatency.c.o'.
../benchmarks/gem_syslatency.c: In function 'sys_wait':
../benchmarks/gem_syslatency.c:180:29: warning: assignment to 'void (*)(union sigval)' from 'int' makes pointer from integer without a cast [-Wint-conversion]
180 | sev.sigev_notify_thread_id = gettid();
| ^
[52/366] Compiling C object 'lib/76b5a35@@igt-igt_aux_c@sta/igt_aux.c.o'.
../lib/igt_aux.c: In function 'igt_sigiter_start':
../lib/igt_aux.c:187:30: warning: assignment to 'void (*)(union sigval)' from 'pid_t' {aka 'int'} makes pointer from integer without a cast [-Wint-conversion]
187 | sev.sigev_notify_thread_id = __igt_sigiter.tid;
| ^
../lib/igt_aux.c: In function 'igt_start_siglatency':
../lib/igt_aux.c:1615:29: warning: assignment to 'void (*)(union sigval)' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1615 | sev.sigev_notify_thread_id = gettid();
| ^
```
There's still the problem that the build sometimes hangs, tried adding `disable_parallel_build=yes` but no success. I could reach the end when manually chrooting though.
next prev parent reply other threads:[~2019-11-12 9:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 23:33 [PR PATCH] " voidlinux-github
2019-11-12 9:21 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-12 9:26 ` voidlinux-github [this message]
2019-11-12 9:32 ` voidlinux-github
2019-11-12 9:33 ` voidlinux-github
2019-11-12 13:28 ` voidlinux-github
2019-11-12 13:28 ` voidlinux-github
2019-11-12 13:38 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-12 13:38 ` voidlinux-github
2019-11-12 14:04 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-12 14:06 ` voidlinux-github
2019-11-12 14:17 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-12 15:48 ` voidlinux-github
2019-11-12 15:49 ` voidlinux-github
2019-11-12 15:50 ` voidlinux-github
2019-11-12 15:51 ` voidlinux-github
2019-11-12 15:51 ` voidlinux-github
2019-11-12 15:52 ` voidlinux-github
2019-11-12 15:52 ` voidlinux-github
2019-11-12 15:54 ` voidlinux-github
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=20191112092604.IHu0qxMoRy4JMr0Qz11wK6_nLkBFO4Ewb1IOdikW2LA@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).