Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Google (abseil-cpp/protobuf/grpc) update
Date: Thu, 22 Feb 2024 00:38:22 +0100	[thread overview]
Message-ID: <20240221233822.1E12324B36@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48772@inbox.vuxu.org>

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

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

Google (abseil-cpp/protobuf/grpc) update
https://github.com/void-linux/void-packages/pull/48772

Description:
I don't really use Protobuf or gRPC anymore, but noticed the packages are a bit outdated, so I'll let this sit for a bit and merge if nobody raises any issues for awhile.

This PR includes a few GCC 13 fixes necessary to build some packages (generally including `<cstdint>`) even with the old versions of Googleware.

Also, in VLC, I'm dropping `libplacebo` to allow https://github.com/void-linux/void-packages/pull/47361 to proceed. That change has nothing to do with the Googleware updates, but saves us from another needless revbump of VLC.

@leahneukirchen: if you have any insight on getting `justbuild` to work, please let me know. The bootstrap pulls in old gRPC and abseil, and then the linker panics when it looks for old abseil symbols in the new abseil libraries.

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

#### Local build testing
Except for `justbuild`, everything builds on:
- [x] x86_64
- [x] x86_64-musl
- [x] i686
- [x] aarch64
- [x] aarch64-musl
- [x] armv6l
- [x] armv6l-musl
- [x] armv7l
- [x] armv7l-musl

[ci skip]

      parent reply	other threads:[~2024-02-21 23:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 16:42 [PR PATCH] " ahesford
2024-02-16 16:49 ` [PR PATCH] [Updated] " ahesford
2024-02-17  1:41 ` ahesford
2024-02-17  1:53 ` ahesford
2024-02-17 14:37 ` leahneukirchen
2024-02-17 15:11 ` [PR PATCH] [Updated] " ahesford
2024-02-17 17:31 ` ahesford
2024-02-21 23:27 ` ahesford
2024-02-21 23:38 ` ahesford
2024-02-21 23:38 ` ahesford [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=20240221233822.1E12324B36@inbox.vuxu.org \
    --to=ahesford@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).