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: dev-libs/libgcrypt/files/, dev-libs/libgcrypt/
Date: Thu, 10 Feb 2022 12:05:56 +0000 (UTC)	[thread overview]
Message-ID: <1644494745.c20b92558b8c696c07ad55aa46f21bb2d931703b.sam@gentoo> (raw)

commit:     c20b92558b8c696c07ad55aa46f21bb2d931703b
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 10 11:57:23 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Feb 10 12:05:45 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c20b9255

dev-libs/libgcrypt: add musl build patch for 1.10.0

Signed-off-by: Sam James <sam <AT> gentoo.org>

 ...gcrypt-1.10.0-musl-jitterentropy-includes.patch | 26 ++++++++++++++++++++++
 dev-libs/libgcrypt/libgcrypt-1.10.0.ebuild         |  2 ++
 2 files changed, 28 insertions(+)

diff --git a/dev-libs/libgcrypt/files/libgcrypt-1.10.0-musl-jitterentropy-includes.patch b/dev-libs/libgcrypt/files/libgcrypt-1.10.0-musl-jitterentropy-includes.patch
new file mode 100644
index 000000000000..205944dd7a1b
--- /dev/null
+++ b/dev-libs/libgcrypt/files/libgcrypt-1.10.0-musl-jitterentropy-includes.patch
@@ -0,0 +1,26 @@
+https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=ffaef0be613121d3ee37867d82932a7a30c2bc6d
+
+From: Heiko Becker <heirecka@exherbo.org>
+Date: Thu, 3 Feb 2022 22:46:41 +0000
+Subject: [PATCH] jitterentropy: Include <fcntl.h> and <limits.h>
+
+* random/jitterentropy-base-user.h: Include <fcntl.h> for O_RDONLY
+* random/jitterentropy-base-user.h: Include <limits.h> for LONG_MAX
+
+--
+
+Fixes the build with musl libc.
+
+Signed-off-by: Heiko Becker <heirecka@exherbo.org>
+--- a/random/jitterentropy-base-user.h
++++ b/random/jitterentropy-base-user.h
+@@ -39,6 +39,9 @@
+  * DAMAGE.
+  */
+ 
++#include <fcntl.h>
++#include <limits.h>
++
+ #ifndef GCRYPT_JITTERENTROPY_BASE_USER_H
+ #define GCRYPT_JITTERENTROPY_BASE_USER_H
+ 

diff --git a/dev-libs/libgcrypt/libgcrypt-1.10.0.ebuild b/dev-libs/libgcrypt/libgcrypt-1.10.0.ebuild
index 513ccf607690..de6cdbebc481 100644
--- a/dev-libs/libgcrypt/libgcrypt-1.10.0.ebuild
+++ b/dev-libs/libgcrypt/libgcrypt-1.10.0.ebuild
@@ -38,6 +38,8 @@ BDEPEND="doc? ( virtual/texi2dvi )
 PATCHES=(
 	"${FILESDIR}"/${PN}-multilib-syspath.patch
 	"${FILESDIR}"/${PN}-powerpc-darwin.patch
+
+	"${FILESDIR}"/${P}-musl-jitterentropy-includes.patch
 )
 
 MULTILIB_CHOST_TOOLS=(


             reply	other threads:[~2022-02-10 12:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 12:05 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-16  5:17 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgcrypt/files/, dev-libs/libgcrypt/ Sam James
2024-10-17  4:12 Sam James
2024-06-24 23:59 Mike Gilbert
2024-03-04  3:00 Sam James
2022-12-05  3:58 Sam James
2022-06-15 20:58 Sam James
2021-12-27 12:57 Fabian Groffen
2021-01-29 20:45 Sam James
2017-01-16 23:34 Kristian Fiskerstrand
2015-12-01  6:16 Alon Bar-Lev

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=1644494745.c20b92558b8c696c07ad55aa46f21bb2d931703b.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