From: "Martin Mokrejs" <mmokrejs@fold.natur.cuni.cz>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-biology/amos/, sci-biology/amos/files/
Date: Wed, 7 Mar 2018 12:29:33 +0000 (UTC) [thread overview]
Message-ID: <1520425753.2b34e4019d8a95ce7efd7db67337571a8dfd18be.mmokrejs@gentoo> (raw)
commit: 2b34e4019d8a95ce7efd7db67337571a8dfd18be
Author: Martin Mokrejs <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
AuthorDate: Wed Mar 7 12:29:13 2018 +0000
Commit: Martin Mokrejs <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
CommitDate: Wed Mar 7 12:29:13 2018 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=2b34e401
sci-biology/amos: fix include path from -I$(top_builddir) to -I$(top_builddir)
The include path is wrong when we use separate build directory.
In file included from src/Bambus/Bundler/Utilities_Bundler.cc:4:0:
src/Bambus/Bundler/Utilities_Bundler.hh:16:26: fatal error: Contig_AMOS.hh: No such file or directory
https://sourceforge.net/p/amos/mailman/amos-help/thread/197db37d-d83e-1371-022b-2866c5686bd9%40fold.natur.cuni.cz/#msg36246774
Package-Manager: Portage-2.3.24, Repoman-2.3.6
sci-biology/amos/amos-9999.ebuild | 14 +++++++++++++-
sci-biology/amos/files/amos-9999-fix-include-paths.patch | 13 +++++++++++++
2 files changed, 26 insertions(+), 1 deletion(-)
diff --git a/sci-biology/amos/amos-9999.ebuild b/sci-biology/amos/amos-9999.ebuild
index 97ae851a3..2c911603d 100644
--- a/sci-biology/amos/amos-9999.ebuild
+++ b/sci-biology/amos/amos-9999.ebuild
@@ -3,8 +3,10 @@
EAPI=5
+PYTHON_COMPAT=( python2_7 )
+
PERL_EXPORT_PHASE_FUNCTIONS=no
-inherit perl-module eutils toolchain-funcs
+inherit perl-module eutils toolchain-funcs autotools flag-o-matic python-single-r1 qmake-utils
AUTOTOOLS_AUTORECONF=true
inherit autotools-utils git-r3
@@ -37,6 +39,16 @@ RDEPEND="${DEPEND}
# ERROR: Could not open file LIBGUESTFS_PATH=/usr/share/guestfs/appliance/
# $
+src_prepare() {
+ epatch "${FILESDIR}"/"${P}"-fix-include-paths.patch
+ default
+ eautoreconf
+
+ # prevent GCC 6 log pollution due
+ # to hash_map deprecation in C++11
+ append-cxxflags -Wno-cpp
+}
+
src_install() {
default
python_replicate_script "${ED}"/usr/bin/goBambus2
diff --git a/sci-biology/amos/files/amos-9999-fix-include-paths.patch b/sci-biology/amos/files/amos-9999-fix-include-paths.patch
new file mode 100644
index 000000000..a6e8dc9f0
--- /dev/null
+++ b/sci-biology/amos/files/amos-9999-fix-include-paths.patch
@@ -0,0 +1,13 @@
+--- src/Bambus/Bundler/Makefile.am.old 2018-07-03 12:52:17.306095693 +0200
++++ src/Bambus/Bundler/Makefile.am 2018-07-03 12:52:19.506101530 +0200
+@@ -78,8 +78,8 @@
+ ##-- libBundler.a
+ libBundler_a_CPPFLAGS = \
+ $(BOOST_CXXFLAGS) \
+- -I$(top_builddir)/src/GNU \
+- -I$(top_builddir)/src/AMOS
++ -I$(top_srcdir)/src/GNU \
++ -I$(top_srcdir)/src/AMOS
+ ## because some system headers will be built if necessary
+ libBundler_a_LIBADD = \
+ $(LIBOBJS:%=$(top_builddir)/src/GNU/%) \
next reply other threads:[~2018-03-07 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 12:29 Martin Mokrejs [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-03 4:02 [gentoo-commits] proj/sci:master commit in: sci-biology/amos/, sci-biology/amos/files/ Benda XU
2015-03-31 20:19 Martin Mokrejs
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=1520425753.2b34e4019d8a95ce7efd7db67337571a8dfd18be.mmokrejs@gentoo \
--to=mmokrejs@fold.natur.cuni.cz \
--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