From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/mesa/, media-libs/mesa/files/
Date: Fri, 9 Nov 2018 23:33:12 +0000 (UTC) [thread overview]
Message-ID: <1541806342.59c06ef2ca463bb033bec7aaac3ea6c6404d94e9.mattst88@gentoo> (raw)
commit: 59c06ef2ca463bb033bec7aaac3ea6c6404d94e9
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 9 23:30:15 2018 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Fri Nov 9 23:32:22 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=59c06ef2
media-libs/mesa: Add patch to fix typo in meson.build
Fixes build failures on at least ppc and sparc. Patch should be in
18.2.5 and 18.3.0.
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
.../mesa/files/mesa-18.2.4-meson-fix-libatomic-tests.patch | 13 +++++++++++++
media-libs/mesa/mesa-18.2.4.ebuild | 1 +
2 files changed, 14 insertions(+)
diff --git a/media-libs/mesa/files/mesa-18.2.4-meson-fix-libatomic-tests.patch b/media-libs/mesa/files/mesa-18.2.4-meson-fix-libatomic-tests.patch
new file mode 100644
index 00000000000..d8709eae8f7
--- /dev/null
+++ b/media-libs/mesa/files/mesa-18.2.4-meson-fix-libatomic-tests.patch
@@ -0,0 +1,13 @@
+diff --git a/meson.build b/meson.build
+index 690e7d3d8aa..fb08e905ebd 100644
+--- a/meson.build
++++ b/meson.build
+@@ -906,7 +906,7 @@ if not cc.links('''#include <stdint.h>
+ return __sync_add_and_fetch(&v, (uint64_t)1);
+ }''',
+ name : 'GCC 64bit atomics')
+- pre_args += '-DMISSING_64_BIT_ATOMICS'
++ pre_args += '-DMISSING_64BIT_ATOMICS'
+ endif
+
+ # TODO: shared/static? Is this even worth doing?
diff --git a/media-libs/mesa/mesa-18.2.4.ebuild b/media-libs/mesa/mesa-18.2.4.ebuild
index dbdf7d53042..a955d518e07 100644
--- a/media-libs/mesa/mesa-18.2.4.ebuild
+++ b/media-libs/mesa/mesa-18.2.4.ebuild
@@ -233,6 +233,7 @@ x86? (
PATCHES=(
"${FILESDIR}"/${P}-meson-link-gallium-nine-with-pthreads.patch
+ "${FILESDIR}"/${P}-meson-fix-libatomic-tests.patch
)
llvm_check_deps() {
next reply other threads:[~2018-11-09 23:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 23:33 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-17 3:58 [gentoo-commits] repo/gentoo:master commit in: media-libs/mesa/, media-libs/mesa/files/ Matt Turner
2024-03-28 16:05 Matt Turner
2024-02-15 14:51 Matt Turner
2024-01-24 17:00 Matt Turner
2023-12-20 18:56 Matt Turner
2023-09-27 1:52 Sam James
2023-05-12 17:18 Matt Turner
2023-05-12 17:18 Matt Turner
2023-04-25 15:20 Matt Turner
2020-06-23 3:44 Matt Turner
2018-11-02 21:24 Matt Turner
2018-09-29 17:19 Matt Turner
2017-12-05 1:17 Matt Turner
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=1541806342.59c06ef2ca463bb033bec7aaac3ea6c6404d94e9.mattst88@gentoo \
--to=mattst88@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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