From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] opencollada: add patch to fix incompatibility with nullptr
Date: Fri, 21 Jul 2023 21:43:37 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45181@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
There is a new pull request by Johnnynator against master on the void-packages repository
https://github.com/Johnnynator/void-packages opencollada
https://github.com/void-linux/void-packages/pull/45181
opencollada: add patch to fix incompatibility with nullptr
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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
-->
A patch file from https://github.com/void-linux/void-packages/pull/45181.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-opencollada-45181.patch --]
[-- Type: text/x-diff, Size: 1241 bytes --]
From 4b60ec2c068b633544eee5e87dc23cba90604b5e Mon Sep 17 00:00:00 2001
From: John <me@johnnynator.dev>
Date: Fri, 21 Jul 2023 21:34:38 +0200
Subject: [PATCH] opencollada: add patch to fix incompatibility with nullptr
---
srcpkgs/opencollada/patches/musl-1.2.3.patch | 11 +++++++++++
1 file changed, 11 insertions(+)
create mode 100644 srcpkgs/opencollada/patches/musl-1.2.3.patch
diff --git a/srcpkgs/opencollada/patches/musl-1.2.3.patch b/srcpkgs/opencollada/patches/musl-1.2.3.patch
new file mode 100644
index 0000000000000..d203fc46e4990
--- /dev/null
+++ b/srcpkgs/opencollada/patches/musl-1.2.3.patch
@@ -0,0 +1,11 @@
+--- a/COLLADAStreamWriter/src/COLLADASWLibraryAnimations.cpp 2018-11-26 23:43:10.000000000 +0100
++++ - 2023-02-23 13:47:42.819812753 +0100
+@@ -62,7 +62,7 @@
+
+ //---------------------------------------------------------------
+ LibraryAnimations::LibraryAnimations ( COLLADASW::StreamWriter * streamWriter )
+- : Library ( streamWriter, CSWC::CSW_ELEMENT_LIBRARY_ANIMATIONS ), mOpenAnimations ( NULL )
++ : Library ( streamWriter, CSWC::CSW_ELEMENT_LIBRARY_ANIMATIONS ), mOpenAnimations ( {} )
+ {}
+
+ //---------------------------------------------------------------
next reply other threads:[~2023-07-21 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 19:43 Johnnynator [this message]
2023-10-20 1:45 ` github-actions
2023-11-03 1:45 ` [PR PATCH] [Closed]: " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45181@inbox.vuxu.org \
--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).