From: Jason Gunthorpe <jgg@ziepe.ca>
To: Benjamin Drung <benjamin.drung@cloud.ionos.com>,
Gal Pressman <galpress@amazon.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: failed armel build of rdma-core 24.0-1
Date: Wed, 10 Jul 2019 16:23:16 -0300 [thread overview]
Message-ID: <20190710192316.GH4051@ziepe.ca> (raw)
In-Reply-To: <156275862123.1841.4329369138979653018@wuiet.debian.org>
Benjamin,
Can you confirm that something like this fixes these build problems?
diff --git a/debian/rules b/debian/rules
index 07c9c145ff090c..facb45170eacfc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -63,6 +63,7 @@ ifneq (,$(filter-out $(COHERENT_DMA_ARCHS),$(DEB_HOST_ARCH)))
test -e debian/$$package.install.backup || cp debian/$$package.install debian/$$package.install.backup; \
done
sed -i '/mlx[45]/d' debian/ibverbs-providers.install debian/libibverbs-dev.install debian/rdma-core.install
+ sed -i '/efa/d' debian/ibverbs-providers.install debian/libibverbs-dev.install debian/rdma-core.install
endif
DESTDIR=$(CURDIR)/debian/tmp ninja -C build-deb install
On Wed, Jul 10, 2019 at 11:37:01AM -0000, Debian buildds wrote:
> * Source package: rdma-core
> * Version: 24.0-1
> * Architecture: armel
> * State: failed
> * Suite: sid
> * Builder: antheil.debian.org
> * Build log: https://buildd.debian.org/status/fetch.php?pkg=rdma-core&arch=armel&ver=24.0-1&stamp=1562758620&file=log
>
> Please note that these notifications do not necessarily mean bug reports
> in your package but could also be caused by other packages, temporary
> uninstallabilities and arch-specific breakages. A look at the build log
> despite this disclaimer would be appreciated however.
next parent reply other threads:[~2019-07-10 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <156275862123.1841.4329369138979653018@wuiet.debian.org>
2019-07-10 19:23 ` Jason Gunthorpe [this message]
2019-07-11 6:35 ` failed armel build of rdma-core 24.0-1 Gal Pressman
2019-07-11 7:07 ` Leon Romanovsky
2019-07-11 8:00 ` Gal Pressman
2019-07-11 11:11 ` Leon Romanovsky
2019-07-11 10:53 ` Benjamin Drung
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=20190710192316.GH4051@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=benjamin.drung@cloud.ionos.com \
--cc=galpress@amazon.com \
--cc=linux-rdma@vger.kernel.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