Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: pianobar: fix build
Date: Thu, 24 Mar 2022 15:43:34 +0100	[thread overview]
Message-ID: <20220324144334.XGg3UgdYFjtkou6PRuP4zKyUMuuD_xfdmSSJYC7-Gwo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36316@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

pianobar: fix build
https://github.com/void-linux/void-packages/pull/36316

Description:
Currently build fails with:

```
In file included from src/ui.h:28,
                 from src/ui_act.c:34:
src/libpiano/piano.h:32:10: fatal error: gcrypt.h: No such file or directory
   32 | #include <gcrypt.h>
      |          ^~~~~~~~~~
compilation terminated.
make: *** [Makefile:109: src/ui_act.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from src/main.c:51:
src/libpiano/piano.h:32:10: fatal error: gcrypt.h: No such file or directory
   32 | #include <gcrypt.h>
      |          ^~~~~~~~~~
compilation terminated.
make: *** [Makefile:109: src/main.o] Error 1
In file included from src/settings.c:38:
src/libpiano/piano.h:32:10: fatal error: gcrypt.h: No such file or directory
   32 | #include <gcrypt.h>
      |          ^~~~~~~~~~
compilation terminated.
make: *** [Makefile:109: src/settings.o] Error 1
In file included from src/player.h:37,
                 from src/player.c:61:
src/libpiano/piano.h:32:10: fatal error: gcrypt.h: No such file or directory
   32 | #include <gcrypt.h>
      |          ^~~~~~~~~~
compilation terminated.
make: *** [Makefile:109: src/player.o] Error 1
```

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!-- 
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      reply	other threads:[~2022-03-24 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 13:51 [PR PATCH] " tibequadorian
2022-03-24 14:43 ` sgn [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=20220324144334.XGg3UgdYFjtkou6PRuP4zKyUMuuD_xfdmSSJYC7-Gwo@z \
    --to=sgn@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).