public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/jna/
Date: Sat, 12 Jun 2021 09:59:00 +0000 (UTC)	[thread overview]
Message-ID: <1623491683.0bbc0cdf5c9659cec63baf45e9ab6ee909a903f7.fordfrog@gentoo> (raw)

commit:     0bbc0cdf5c9659cec63baf45e9ab6ee909a903f7
Author:     Volkmar W. Pogatzki <gentoo <AT> pogatzki <DOT> net>
AuthorDate: Wed Jun  9 11:04:50 2021 +0000
Commit:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Sat Jun 12 09:54:43 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0bbc0cdf

dev-java/jna: min java restrict to 1.8

It failed to build with java 11

Package-Manager: Portage-3.0.18, Repoman-3.0.2
Signed-off-by: Volkmar W. Pogatzki <gentoo <AT> pogatzki.net>
Closes: https://github.com/gentoo/gentoo/pull/21173
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>

 dev-java/jna/jna-4.2.2-r2.ebuild | 87 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 87 insertions(+)

diff --git a/dev-java/jna/jna-4.2.2-r2.ebuild b/dev-java/jna/jna-4.2.2-r2.ebuild
new file mode 100644
index 00000000000..ea4a7b11f2c
--- /dev/null
+++ b/dev-java/jna/jna-4.2.2-r2.ebuild
@@ -0,0 +1,87 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+JAVA_PKG_IUSE="doc source"
+MAVEN_ID="net.java.dev.jna:jna:4.2.2"
+
+inherit java-pkg-2 java-ant-2 toolchain-funcs
+
+DESCRIPTION="Java Native Access (JNA)"
+HOMEPAGE="https://github.com/java-native-access/jna"
+SRC_URI="https://github.com/java-native-access/jna/archive/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="LGPL-2.1"
+SLOT="4"
+KEYWORDS="~amd64 ~x86"
+IUSE="+awt +nio-buffers test"
+
+REQUIRED_USE="test? ( awt nio-buffers )"
+
+# The tests stall immediately on some systems (not current stable?) when
+# the sandbox is active but pass successfully otherwise. Chewi has not
+# been able to determine why. This began in 4.2.0 as 4.1.0 worked
+# fine. Someone bisect it please. :)
+RESTRICT="test"
+
+CDEPEND="dev-libs/libffi"
+DEPEND="${CDEPEND}
+	virtual/jdk:1.8
+	x11-libs/libXt
+	test? (
+		dev-java/ant-junit:0
+		dev-java/guava:20
+		dev-java/javassist:3
+		dev-java/reflections:0
+	)"
+RDEPEND="${CDEPEND}
+	virtual/jre:1.8"
+BDEPEND="virtual/pkgconfig"
+
+PATCHES=(
+	"${FILESDIR}"/${PV}-build.xml.patch
+	"${FILESDIR}"/${PV}-makefile-flags.patch
+)
+
+JAVA_ANT_REWRITE_CLASSPATH="true"
+EANT_BUILD_TARGET="native jar contrib-jars"
+EANT_EXTRA_ARGS="-Ddynlink.native=true"
+EANT_TEST_EXTRA_ARGS="-Dheadless=true -Djava.io.tmpdir=${T}"
+EANT_TEST_GENTOO_CLASSPATH="guava-20,javassist-3,reflections"
+
+src_prepare() {
+	default
+
+	# delete bundled jars and copy of libffi
+	# except native jars because build.xml needs them all
+	find ! -path "./lib/native/*" -name "*.jar" -delete || die
+	rm -r native/libffi || die
+
+	if ! use awt ; then
+		sed -i -E "s/^(CDEFINES=.*)/\1 -DNO_JAWT/g" native/Makefile || die
+	fi
+
+	if ! use nio-buffers ; then
+		sed -i -E "s/^(CDEFINES=.*)/\1 -DNO_NIO_BUFFERS/g" native/Makefile || die
+	fi
+
+	java-pkg-2_src_prepare
+}
+
+src_configure() {
+	tc-export CC
+}
+
+src_install() {
+	java-pkg_newjar build/${PN}-min.jar
+	java-pkg_dojar contrib/platform/dist/${PN}-platform.jar
+	java-pkg_doso build/native-*/libjnidispatch.so
+
+	use source && java-pkg_dosrc src/*
+	use doc && java-pkg_dojavadoc doc/javadoc
+}
+
+src_test() {
+	java-pkg-2_src_test
+}


             reply	other threads:[~2021-06-12  9:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  9:59 Miroslav Šulc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-29 14:30 [gentoo-commits] repo/gentoo:master commit in: dev-java/jna/ Arthur Zamarin
2024-10-30 11:42 Miroslav Šulc
2024-01-29  8:28 Miroslav Šulc
2024-01-19 10:47 Sam James
2024-01-19 10:07 Sam James
2024-01-19 10:07 Sam James
2023-12-20  9:19 Miroslav Šulc
2023-09-29  5:53 Miroslav Šulc
2023-09-29  5:53 Miroslav Šulc
2023-09-17 14:28 Arthur Zamarin
2023-07-18  9:53 Sam James
2023-06-19 14:18 Sam James
2023-06-19 14:18 Sam James
2023-05-20  9:39 Sam James
2023-05-08 17:36 Sam James
2022-07-22 21:31 Florian Schmaus
2022-07-07  4:03 Miroslav Šulc
2022-07-06 18:26 Arthur Zamarin
2022-07-02 12:23 Agostino Sarubbo
2022-07-02 12:20 Agostino Sarubbo
2022-07-02  7:18 Jakov Smolić
2022-06-15 16:15 Arthur Zamarin
2022-06-15 16:15 Arthur Zamarin
2022-06-15 14:30 Agostino Sarubbo
2022-06-15  7:36 Jakov Smolić
2022-05-12  7:09 Florian Schmaus
2022-04-19  7:43 Florian Schmaus
2022-01-14 15:07 Arthur Zamarin
2022-01-09  9:07 Miroslav Šulc
2022-01-08 13:08 Miroslav Šulc
2022-01-08 10:17 Arthur Zamarin
2022-01-08 10:17 Arthur Zamarin
2021-11-26  9:23 Sam James
2021-11-12  8:16 Agostino Sarubbo
2021-11-11 11:35 Agostino Sarubbo
2021-07-10 18:54 Sam James
2021-06-14  6:39 Sergei Trofimovich
2021-06-12 13:19 Miroslav Šulc
2021-04-25 17:52 Miroslav Šulc
2020-11-16 22:53 Sergei Trofimovich
2018-11-04 15:16 Pacho Ramos
2018-03-17 13:37 Pacho Ramos
2018-03-17 13:37 Pacho Ramos
2016-11-06 11:19 James Le Cuirot
2016-11-06 11:19 James Le Cuirot
2016-06-28 12:29 Patrick Lauer
2016-05-11 21:07 James Le Cuirot
2015-09-30 23:07 Patrice Clement

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=1623491683.0bbc0cdf5c9659cec63baf45e9ab6ee909a903f7.fordfrog@gentoo \
    --to=fordfrog@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