From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libxml2: update to 2.12.5.
Date: Mon, 19 Feb 2024 07:56:51 +0100 [thread overview]
Message-ID: <20240219065651.2A00C2B4B9@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48826@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/48826#issuecomment-1951808204
Comment:
> [php/php-src@0a39890](https://github.com/php/php-src/commit/0a39890c967aa57225bb6bdf4821aff7a3a3c082)
Seems like their tests are configured with `--enable-werror`, which we don't do, and implicitly casing away a const is a warning in clang (whereas no such warning exists in gcc). I can still import the patch
next prev parent reply other threads:[~2024-02-19 6:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 5:20 [PR PATCH] " oreo639
2024-02-19 5:26 ` oreo639
2024-02-19 5:30 ` oreo639
2024-02-19 5:51 ` [PR PATCH] [Updated] " oreo639
2024-02-19 6:18 ` sgn
2024-02-19 6:50 ` oreo639
2024-02-19 6:51 ` oreo639
2024-02-19 6:51 ` oreo639
2024-02-19 6:55 ` oreo639
2024-02-19 6:55 ` oreo639
2024-02-19 6:55 ` oreo639
2024-02-19 6:56 ` oreo639
2024-02-19 6:56 ` oreo639 [this message]
2024-02-19 6:57 ` oreo639
2024-02-19 7:00 ` oreo639
2024-02-19 7:01 ` sgn
2024-02-19 7:21 ` oreo639
2024-02-19 7:22 ` oreo639
2024-02-19 7:23 ` oreo639
2024-02-19 7:37 ` [PR PATCH] [Updated] " oreo639
2024-02-19 12:41 ` oreo639
2024-02-19 12:59 ` oreo639
2024-02-19 14:32 ` oreo639
2024-02-19 14:53 ` oreo639
2024-02-19 14:57 ` oreo639
2024-02-25 3:45 ` oreo639
2024-02-25 3:59 ` oreo639
2024-02-25 10:05 ` oreo639
2024-02-27 2:39 ` oreo639
2024-03-05 23:22 ` oreo639
2024-03-05 23:41 ` oreo639
2024-03-06 0:35 ` [PR PATCH] [Merged]: " oreo639
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=20240219065651.2A00C2B4B9@inbox.vuxu.org \
--to=oreo639@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).