From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Update gcompat to 0.9.0, use dynamic musl-obstack
Date: Sat, 08 Aug 2020 16:23:38 +0200 [thread overview]
Message-ID: <20200808142338.pFau0dHp151szrTK9uXDi1S7LSY-2el9t0DBl7F4aNE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23432@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
There's a merged pull request on the void-packages repository
Update gcompat to 0.9.0, use dynamic musl-obstack
https://github.com/void-linux/void-packages/pull/23432
Description:
Okay, so this is a biggie PR, and I do need help for making some decisions.
- So, basically, `gcompat` can do Spotify now, on Adélie. I am working on debugging it on Void, because it isn't working completely yet. If I can't get it working soon, I will leave the spotify commit out of this one.
- I enabled `obstack` in `gcompat`, by enabling the dynamic lib in `musl-obstack`. This completely fixes #22616, which needed obstack and `__strftime_l` symbols (the latter was fixed by gcompat itself).
- I split `musl-obstack-devel`.
- I switched package dependencies to `musl-obstack-devel`, but they ended up depending on the dynamic version of obstack. Is this bad? Is there some way to solve this? Perhaps two devel sub packages, one for dynamic and one for static linking?
prev parent reply other threads:[~2020-08-08 14:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 23:50 [PR PATCH] [RFC] Update gcompat to 0.9.0, add spotify to musl, " ericonr
2020-07-06 23:54 ` [RFC][WIP] " ericonr
2020-07-07 4:59 ` [PR PATCH] [Updated] " ericonr
2020-07-07 20:48 ` kqo
2020-07-07 20:52 ` ericonr
2020-07-07 20:52 ` [PR PATCH] [Updated] " ericonr
2020-07-07 20:53 ` ericonr
2020-07-09 2:50 ` ericonr
2020-07-09 8:59 ` ericonr
2020-07-09 23:39 ` [PR PATCH] [Updated] " ericonr
2020-07-14 18:25 ` ericonr
2020-07-14 18:26 ` Update gcompat to 0.9.0, " ericonr
2020-07-15 17:03 ` ericonr
2020-07-20 4:48 ` [PR PATCH] [Updated] " ericonr
2020-07-20 4:51 ` ericonr
2020-07-28 2:58 ` ericonr
2020-07-28 3:02 ` ericonr
2020-07-28 5:11 ` pullmoll
2020-07-28 5:12 ` [PR REVIEW] " pullmoll
2020-07-28 5:16 ` pullmoll
2020-07-28 5:21 ` ericonr
2020-07-28 5:22 ` ericonr
2020-07-29 17:27 ` djames1
2020-08-08 14:23 ` Johnnynator [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=20200808142338.pFau0dHp151szrTK9uXDi1S7LSY-2el9t0DBl7F4aNE@z \
--to=johnnynator@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).