Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: utils: sofprobeclient: fix musl build
Date: Tue,  2 Jun 2026 20:28:32 +0200 (CEST)	[thread overview]
Message-ID: <18b55705d213f600-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/tinycompress/pr/37@alsa-project.org>

alsa-project/tinycompress pull request #37 was opened from bkuhls:

With musl C library, we see following build failure:
```
probes_demux.c: In function ‘parser_parse_data’:
probes_demux.c:321:9: error: unknown type name ‘uint’; did you mean ‘int’?
  321 |         uint i = 0;

probes_demux.c:386:25: error: unknown type name ‘uint’; did you mean ‘int’?
  386 |                         uint data_to_copy;
```
uint is defined in <sys/types.h> header. It is usually included by <stdlib.h> but in musl stdlib.h doesn't include it.

Request URL   : https://github.com/alsa-project/tinycompress/pull/37
Patch URL     : https://github.com/alsa-project/tinycompress/pull/37.patch
Repository URL: https://github.com/alsa-project/tinycompress

           reply	other threads:[~2026-06-02 18:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alsa-project/tinycompress/pr/37@alsa-project.org>]

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=18b55705d213f600-webhooks-bot@alsa-project.org \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.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