From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gstreamer1: add checkdepends
Date: Thu, 11 Feb 2021 00:49:47 +0100 [thread overview]
Message-ID: <20210210234947.1gmCityd3u77oDQGsPkFC0ItG-jO2Pl_zdn1_w3m1ig@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28657@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]
There's a merged pull request on the void-packages repository
gstreamer1: add checkdepends
https://github.com/void-linux/void-packages/pull/28657
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [x] armv7l
- [x] armv6l-musl
-->
I noticed when building the `gstreamer1` package with `xbps-src` that it warns about missing libraries:
![1612995217](https://user-images.githubusercontent.com/30329373/107582857-52f66a00-6bb7-11eb-884a-1cd5c5c497c3.png)
![1612995198](https://user-images.githubusercontent.com/30329373/107582864-54279700-6bb7-11eb-86ac-230a905bd63c.png)
Furthermore, I notice that the [PKGBUILD](https://github.com/archlinux/svntogit-packages/blob/packages/gstreamer/trunk/PKGBUILD) on Arch includes these libraries in their template. This might help with [this](https://github.com/void-linux/void-packages/issues/25852) issue. I notice that durring the build is says that pkg-config can't find gstreamer-1.0.pc in `PKG_CONFIG_PATH`. I used `xlocate gstreamer-1.0.pc` and tried adding, as a result:
```sh
export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:${DESTDIR}/usr/lib/pkgconfig"
```
as that is the directory where `gstreamer-1.0.pc` is located, but the same warning occurs.
prev parent reply other threads:[~2021-02-10 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 22:53 [PR PATCH] gstreamer1: add missing makedepends kawaiiamber
2021-02-10 23:01 ` ericonr
2021-02-10 23:05 ` kawaiiamber
2021-02-10 23:06 ` Johnnynator
2021-02-10 23:07 ` Duncaen
2021-02-10 23:08 ` Duncaen
2021-02-10 23:10 ` [PR PATCH] [Updated] " kawaiiamber
2021-02-10 23:11 ` kawaiiamber
2021-02-10 23:20 ` gstreamer1: add checkdepends kawaiiamber
2021-02-10 23:49 ` ericonr
2021-02-10 23:49 ` ericonr [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=20210210234947.1gmCityd3u77oDQGsPkFC0ItG-jO2Pl_zdn1_w3m1ig@z \
--to=ericonr@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).