From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/nautilus/, gnome-base/nautilus/files/
Date: Sat, 1 Oct 2022 03:16:51 +0000 (UTC) [thread overview]
Message-ID: <1664594064.a1b6c92b768d8ed8f0b34e057c14fda689adf12b.sam@gentoo> (raw)
commit: a1b6c92b768d8ed8f0b34e057c14fda689adf12b
Author: Leonardo Hernández Hernández <leohdz172 <AT> protonmail <DOT> com>
AuthorDate: Sat Oct 1 02:04:55 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Oct 1 03:14:24 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1b6c92b
gnome-base/nautilus: fix build with clang
Signed-off-by: Leonardo Hernández Hernández <leohdz172 <AT> protonmail.com>
Closes: https://github.com/gentoo/gentoo/pull/27549
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../nautilus/files/43.0-fix-clang-build.patch | 30 ++++++++++++++++++++++
gnome-base/nautilus/nautilus-43.0.ebuild | 1 +
2 files changed, 31 insertions(+)
diff --git a/gnome-base/nautilus/files/43.0-fix-clang-build.patch b/gnome-base/nautilus/files/43.0-fix-clang-build.patch
new file mode 100644
index 000000000000..ec8fbd90ac1a
--- /dev/null
+++ b/gnome-base/nautilus/files/43.0-fix-clang-build.patch
@@ -0,0 +1,30 @@
+From 68b050ac0f60b1f02767276643cba8eb701f9884 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Leonardo=20Hern=C3=A1ndez=20Hern=C3=A1ndez?=
+ <leohdz172@protonmail.com>
+Date: Fri, 30 Sep 2022 17:35:50 -0500
+Subject: [PATCH] fix conflicting types for nautilus_file_get{u,g}id
+
+when building with clang
+---
+ src/nautilus-file.h | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/nautilus-file.h b/src/nautilus-file.h
+index 9b0613e98..57cca177f 100644
+--- a/src/nautilus-file.h
++++ b/src/nautilus-file.h
+@@ -244,9 +244,9 @@ gboolean nautilus_file_can_get_owner (Nautilu
+ gboolean nautilus_file_can_set_owner (NautilusFile *file);
+ gboolean nautilus_file_can_get_group (NautilusFile *file);
+ gboolean nautilus_file_can_set_group (NautilusFile *file);
+-uid_t nautilus_file_get_uid (NautilusFile *file);
++const uid_t nautilus_file_get_uid (NautilusFile *file);
+ char * nautilus_file_get_owner_name (NautilusFile *file);
+-gid_t nautilus_file_get_gid (NautilusFile *file);
++const gid_t nautilus_file_get_gid (NautilusFile *file);
+ char * nautilus_file_get_group_name (NautilusFile *file);
+ GList * nautilus_get_user_names (void);
+ GList * nautilus_get_all_group_names (void);
+--
+GitLab
+
diff --git a/gnome-base/nautilus/nautilus-43.0.ebuild b/gnome-base/nautilus/nautilus-43.0.ebuild
index 44ac74e4207e..8fec2d0f8328 100644
--- a/gnome-base/nautilus/nautilus-43.0.ebuild
+++ b/gnome-base/nautilus/nautilus-43.0.ebuild
@@ -56,6 +56,7 @@ PDEPEND="
PATCHES=(
"${FILESDIR}"/43.0-docs-build.patch # Always install pregenerated manpage, keeping docs option for gtk-doc
"${FILESDIR}"/43.0-optional-gstreamer.patch # Allow controlling audio-video-properties build
+ "${FILESDIR}"/43.0-fix-clang-build.patch # https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/996
)
src_prepare() {
next reply other threads:[~2022-10-01 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:16 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-24 12:00 [gentoo-commits] repo/gentoo:master commit in: gnome-base/nautilus/, gnome-base/nautilus/files/ Mart Raudsepp
2022-09-30 17:55 Matt Turner
2022-03-27 18:58 Matt Turner
2021-12-19 4:53 Matt Turner
2020-11-07 15:23 Mart Raudsepp
2020-03-03 22:20 Mart Raudsepp
2019-08-31 14:06 Mart Raudsepp
2019-03-31 10:14 Mart Raudsepp
2019-03-30 22:21 Mart Raudsepp
2019-03-05 17:53 Mart Raudsepp
2015-11-26 10:51 Gilles Dartiguelongue
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=1664594064.a1b6c92b768d8ed8f0b34e057c14fda689adf12b.sam@gentoo \
--to=sam@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