public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/ffcall/
Date: Mon, 29 Aug 2022 18:39:53 +0000 (UTC)	[thread overview]
Message-ID: <1661798348.d940cbc685337e3464fe994f9bba271a37c2074d.asturm@gentoo> (raw)

commit:     d940cbc685337e3464fe994f9bba271a37c2074d
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 16 21:47:22 2022 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Mon Aug 29 18:39:08 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d940cbc6

dev-libs/ffcall: drop 2.1, EAPI-6--

Closes: https://bugs.gentoo.org/834549
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>

 dev-libs/ffcall/Manifest          |  1 -
 dev-libs/ffcall/ffcall-2.1.ebuild | 60 ---------------------------------------
 2 files changed, 61 deletions(-)

diff --git a/dev-libs/ffcall/Manifest b/dev-libs/ffcall/Manifest
index 70f09ecda210..956d5f041533 100644
--- a/dev-libs/ffcall/Manifest
+++ b/dev-libs/ffcall/Manifest
@@ -1,2 +1 @@
-DIST libffcall-2.1.tar.gz 943235 BLAKE2B ae82663174db084e830b6ff77ceedf8641b3edeb7800952ac4e2772d9033da3e45f46159e6fdae86615dc69fceba39f48d6c75e6cbd41be98f1986fa69d50b3b SHA512 da73375fb45b7d764c06437a517c2a90abf7d5de6afe0a8ca19e6dfafd2a8c7107e39d230ecbc8edfdd5926b16a0c13b7bb9319287047c47de1241b2f6ae805e
 DIST libffcall-2.4.tar.gz 1253767 BLAKE2B 669bf556f082b533eb7d71ebc6fadeac464b1a6054ac8078c9315678929bcfb8ad4b7376b345bcfbb5d2caf9d45179012d4bb5a08ad675f475f58570ae96b7ae SHA512 c9451662764a888e3be21499c29673bfb0e1df4915814da3506db5d395a2b00ea2f0c08d1c9dffebf030179f9347794876ec6ec9e6710b4fc70fd760960335e6

diff --git a/dev-libs/ffcall/ffcall-2.1.ebuild b/dev-libs/ffcall/ffcall-2.1.ebuild
deleted file mode 100644
index d7fb5928fbfe..000000000000
--- a/dev-libs/ffcall/ffcall-2.1.ebuild
+++ /dev/null
@@ -1,60 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-inherit flag-o-matic
-
-MY_PV="libffcall-${PV}"
-
-DESCRIPTION="Build foreign function call interfaces in embedded interpreter"
-HOMEPAGE="https://www.gnu.org/software/libffcall/"
-SRC_URI="mirror://gnu/libffcall/${MY_PV}.tar.gz"
-
-# "Ffcall is under GNU GPL. As a special exception, if used in GNUstep
-# or in derivate works of GNUstep, the included parts of ffcall are
-# under GNU LGPL." -ffcall author
-LICENSE="GPL-2+"
-SLOT="0"
-KEYWORDS="~alpha amd64 ~arm64 ~hppa ~ia64 ppc ppc64 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris ~x86-solaris"
-
-S="${WORKDIR}"/${MY_PV}
-
-src_prepare() {
-	# The build system is a strange mix of autogenerated
-	# files and manual tweaks on top. Uses $CFLAGS / $LDFLAGS randomly.
-	# We are adding them consistently here and a bit over the top:
-	# bugs: #334581
-
-	for mfi in {,*/,*/*/,}Makefile.in
-	do
-		einfo "Patching '${mfi}'"
-		# usually uses only assembler here, but -march=
-		# and -Wa, are a must to pass here.
-		sed -e 's/$(CC) /&$(CFLAGS) /g' \
-			-i "${mfi}" || die
-	done
-	eapply_user
-}
-
-src_configure() {
-	append-flags -fPIC
-
-	# Doc goes in datadir
-	econf \
-		--datadir="${EPREFIX}"/usr/share/doc/${PF} \
-		--enable-shared \
-		--disable-static
-}
-
-src_compile() {
-	# TODO. Remove -j1
-	emake -j1
-}
-
-src_install() {
-	dodoc NEWS README
-	dodir /usr/share/man
-	default
-	find "${ED}" -name '*.la' -delete || die
-}


             reply	other threads:[~2022-08-29 18:39 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 18:39 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-26  6:06 [gentoo-commits] repo/gentoo:master commit in: dev-libs/ffcall/ Arthur Zamarin
2025-04-26  4:12 Sam James
2025-04-10 10:38 Sam James
2024-11-21 13:47 Jakov Smolić
2024-11-18 11:11 Sam James
2024-11-18 11:11 Sam James
2024-11-18 11:11 Sam James
2024-11-18 11:11 Sam James
2024-11-18  9:36 Sam James
2024-05-02  4:32 Sam James
2022-06-23 19:50 Arthur Zamarin
2022-05-14 21:52 Jakov Smolić
2022-04-28 15:05 Jakov Smolić
2022-03-10 10:10 Jakov Smolić
2022-03-10  9:13 Agostino Sarubbo
2022-03-10  9:13 Agostino Sarubbo
2022-03-10  9:12 Agostino Sarubbo
2022-03-10  9:03 Jakov Smolić
2022-02-17 11:00 Jakov Smolić
2021-11-19  8:34 Sam James
2020-03-19 22:34 Sergei Trofimovich
2018-05-28  9:13 José María Alonso
2018-05-26  9:28 Mikle Kolyada
2018-05-14 21:19 Tobias Klausmann
2018-05-14  0:16 Aaron Bauman
2018-05-13 22:06 Thomas Deutschmann
2018-05-11 19:21 Sergei Trofimovich
2018-05-10 22:43 Sergei Trofimovich
2018-04-10 16:40 José María Alonso
2017-12-16 16:36 José María Alonso
2017-12-16 16:32 José María Alonso
2017-12-16 16:25 José María Alonso
2017-12-16 10:31 Tobias Klausmann
2017-10-26 20:30 Thomas Deutschmann
2017-10-22 21:42 Tobias Klausmann
2017-10-19 20:55 Sergei Trofimovich
2017-10-18 21:28 Sergei Trofimovich
2017-10-18 21:21 Sergei Trofimovich
2017-09-14 15:41 José María Alonso
2017-07-14  7:45 Sergei Trofimovich
2017-07-02 17:05 Alexis Ballier
2017-06-30  7:32 José María Alonso
2017-06-27 10:03 José María Alonso
2017-06-12  8:58 Michael Palimaka

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=1661798348.d940cbc685337e3464fe994f9bba271a37c2074d.asturm@gentoo \
    --to=asturm@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