public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/samba/, net-fs/samba/files/
Date: Fri, 24 Jun 2022 05:26:24 +0000 (UTC)	[thread overview]
Message-ID: <1656048369.9923d7331d1189316726fcab47ba89a2623f82ab.sam@gentoo> (raw)

commit:     9923d7331d1189316726fcab47ba89a2623f82ab
Author:     brahmajit das <brahmajit.xyz <AT> gmail <DOT> com>
AuthorDate: Tue Jun 21 05:48:08 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jun 24 05:26:09 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9923d733

net-fs/samba: Apply the netdb defines patch

NETDB_INTERNAL and NETDB_INTERNAL are not defined in musl as a result
the build is failing.

Acked-by: David Seifert <soap <AT> gentoo.org>
Closes: https://bugs.gentoo.org/835017
Closes: https://bugs.gentoo.org/832629
Signed-off-by: brahmajit das <brahmajit.xyz <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/26016
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-fs/samba/files/samba-4.16.1-netdb-defines.patch | 21 +++++++++++++++++++++
 net-fs/samba/samba-4.16.1.ebuild                    |  1 +
 2 files changed, 22 insertions(+)

diff --git a/net-fs/samba/files/samba-4.16.1-netdb-defines.patch b/net-fs/samba/files/samba-4.16.1-netdb-defines.patch
new file mode 100644
index 000000000000..40aeaa22bfae
--- /dev/null
+++ b/net-fs/samba/files/samba-4.16.1-netdb-defines.patch
@@ -0,0 +1,21 @@
+# Define NETDB_INTERNAL and NETDB_SUCCESS if they are not defined
+#
+# Gentoo bug 832629 and 835017
+
+--- a/nsswitch/wins.c
++++ b/nsswitch/wins.c
+@@ -40,6 +40,14 @@ static pthread_mutex_t wins_nss_mutex = PTHREAD_MUTEX_INITIALIZER;
+ #define INADDRSZ 4
+ #endif
+
++#ifndef NETDB_INTERNAL
++#define NETDB_INTERNAL -1
++#endif
++
++#ifndef NETDB_SUCCESS
++#define NETDB_SUCCESS 0
++#endif
++
+ _PUBLIC_ON_LINUX_
+ NSS_STATUS _nss_wins_gethostbyname_r(const char *hostname,
+ 				     struct hostent *he,

diff --git a/net-fs/samba/samba-4.16.1.ebuild b/net-fs/samba/samba-4.16.1.ebuild
index a7d3fa8bb5d3..8b16a80d66cb 100644
--- a/net-fs/samba/samba-4.16.1.ebuild
+++ b/net-fs/samba/samba-4.16.1.ebuild
@@ -141,6 +141,7 @@ BDEPEND="${PYTHON_DEPS}
 
 PATCHES=(
 	"${FILESDIR}/${PN}-4.4.0-pam.patch"
+	"${FILESDIR}/${PN}-4.16.1-netdb-defines.patch"
 )
 
 #CONFDIR="${FILESDIR}/$(get_version_component_range 1-2)"


             reply	other threads:[~2022-06-24  5:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  5:26 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-27  4:48 [gentoo-commits] repo/gentoo:master commit in: net-fs/samba/, net-fs/samba/files/ Sam James
2022-09-30  2:46 Sam James
2022-07-29 18:12 Ben Kohler
2021-05-22 20:12 Lars Wendler
2020-02-09 14:46 Ben Kohler
2019-04-09  6:05 Lars Wendler
2018-11-08 17:51 Ian Stakenvicius
2018-05-24  8:12 Lars Wendler
2018-01-23 21:36 Mike Frysinger
2017-12-25 20:52 Lars Wendler
2017-11-13 15:49 Lars Wendler
2017-08-11 21:23 Ian Stakenvicius
2017-01-19  2:44 Lars Wendler
2016-04-13  5:42 Sergey Popov
2016-01-13 22:40 Ian Stakenvicius
2016-01-05 22:58 Victor Ostorga

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=1656048369.9923d7331d1189316726fcab47ba89a2623f82ab.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