From: "Horea Christian" <horea.christ@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-biology/afni/
Date: Fri, 1 Apr 2022 08:22:38 +0000 (UTC) [thread overview]
Message-ID: <1648801353.e3ed6312407f673e0d8d544fd54d625b6492a27a.chymera@gentoo> (raw)
commit: e3ed6312407f673e0d8d544fd54d625b6492a27a
Author: Horea Christian <chr <AT> chymera <DOT> eu>
AuthorDate: Fri Apr 1 08:22:33 2022 +0000
Commit: Horea Christian <horea.christ <AT> gmail <DOT> com>
CommitDate: Fri Apr 1 08:22:33 2022 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=e3ed6312
sci-biology/afni: cleaned up whitespace and unneeded code
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Horea Christian <chr <AT> chymera.eu>
sci-biology/afni/afni-20.1.16.ebuild | 8 ++++----
sci-biology/afni/afni-20.3.03.ebuild | 6 +-----
2 files changed, 5 insertions(+), 9 deletions(-)
diff --git a/sci-biology/afni/afni-20.1.16.ebuild b/sci-biology/afni/afni-20.1.16.ebuild
index 98fdb2397..a95a34cfb 100644
--- a/sci-biology/afni/afni-20.1.16.ebuild
+++ b/sci-biology/afni/afni-20.1.16.ebuild
@@ -46,17 +46,17 @@ src_prepare() {
# Unbundle imcat
sed -e "s/ imcat / /g" \
-i Makefile.INCLUDE || die "Could not edit includes files."
- sed -e "s~CC = /usr/bin/gcc -O2 -m64~CC = $(tc-getCC) \$(CFLAGS)~" \
+ sed -e "s~CC = /usr/bin/gcc -O2 -m64~CC = $(tc-getCC) \$(CFLAGS)~" \
-e "s~CCMIN = /usr/bin/gcc -m64~CCMIN = $(tc-getCC) \$(CFLAGS)~" \
- -e "s~LD = /usr/bin/gcc~LD = $(tc-getCC)~" \
- -e "s~AR = /usr/bin/ar~AR = $(tc-getAR)~" \
+ -e "s~LD = /usr/bin/gcc~LD = $(tc-getCC)~" \
+ -e "s~AR = /usr/bin/ar~AR = $(tc-getAR)~" \
-e "s~RANLIB = /usr/bin/ranlib~RANLIB = $(tc-getRANLIB)~" \
-i Makefile || die "Could not edit Makefile"
# they provide somewhat problematic makefiles :(
sed -e "s~ifeq ($(CC),gcc)~ifeq (1,1)~"\
-i SUMA/SUMA_Makefile || die "Could not edit SUMA/SUMA_Makefile"
# upstream checks if $CC is EXACTLY gcc, else sets variables for Mac
- find "${S}" -iname "*Makefile*" | xargs sed -e "s~/usr/~${EROOT}/usr/~g;" -i
+ find "${S}" -iname "*Makefile*" | xargs sed -e "s~/usr/~${EPREFIX}/usr/~g;" -i
default
}
diff --git a/sci-biology/afni/afni-20.3.03.ebuild b/sci-biology/afni/afni-20.3.03.ebuild
index fab7446bf..a95a34cfb 100644
--- a/sci-biology/afni/afni-20.3.03.ebuild
+++ b/sci-biology/afni/afni-20.3.03.ebuild
@@ -39,10 +39,6 @@ S="${WORKDIR}/${PN}-AFNI_${PV}/src"
BUILD="linux_fedora_19_64"
BIN_CONFLICTS=(qdelaunay whirlgif djpeg cjpeg qhull rbox count mpeg_encode)
-#PATCHES=(
-# "${FILESDIR}/${P}-python.patch"
-#)
-
src_prepare() {
eapply "${FILESDIR}/${P}-python.patch" || die
find -type f -exec sed -i -e "s/-lXp //g" {} +
@@ -60,7 +56,7 @@ src_prepare() {
sed -e "s~ifeq ($(CC),gcc)~ifeq (1,1)~"\
-i SUMA/SUMA_Makefile || die "Could not edit SUMA/SUMA_Makefile"
# upstream checks if $CC is EXACTLY gcc, else sets variables for Mac
- find "${S}" -iname "*Makefile*" | xargs sed -e "s~/usr/~${EROOT}/usr/~g;" -i
+ find "${S}" -iname "*Makefile*" | xargs sed -e "s~/usr/~${EPREFIX}/usr/~g;" -i
default
}
next reply other threads:[~2022-04-01 8:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 8:22 Horea Christian [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-12 11:57 [gentoo-commits] proj/sci:master commit in: sci-biology/afni/ Paul Zander
2024-05-30 21:55 Horea Christian
2024-05-29 8:33 Horea Christian
2024-05-24 13:52 Horea Christian
2024-03-22 21:34 Horea Christian
2022-04-03 8:11 Horea Christian
2022-04-01 15:41 Horea Christian
2021-01-03 3:46 Horea Christian
2021-01-03 3:46 Horea Christian
2020-06-19 16:01 Horea Christian
2020-01-16 18:28 Horea Christian
2019-11-25 18:30 Horea Christian
2019-04-25 8:50 Horea Christian
2018-06-26 1:16 Horea Christian
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=1648801353.e3ed6312407f673e0d8d544fd54d625b6492a27a.chymera@gentoo \
--to=horea.christ@gmail.com \
--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