linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Odd build failure in el7 mock
Date: Wed, 22 Mar 2017 11:44:49 -0400	[thread overview]
Message-ID: <16cf8400-4920-c7ae-e0e5-c77a65a71460@redhat.com> (raw)

I'm attempting to build rdma-core v13 rpms... On my el7 host, they build 
just fine. But when I try to build them in mock (using the epel-7-x86_64 
target), I hit this:

-- Removed runtime path from 
"/builddir/build/BUILDROOT/rdma-core-13-1.el7.centos.x86_64/usr/lib64/libmlx5.so.1.0.13"
CMake Error at providers/mlx5/cmake_install.cmake:98 (FILE):
   file INSTALL cannot find
   "/builddir/build/BUILD/rdma-core-13/providers/mlx5/libmlx5-rdmav2.so".
Call Stack (most recent call first):
   cmake_install.cmake:52 (INCLUDE)


make: *** [install] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.MsCuJ7 (%install)


RPM build errors:
     Bad exit status from /var/tmp/rpm-tmp.MsCuJ7 (%install)
ERROR: Exception(rdma-core-13-1.el7.src.rpm) Config(epel-7-x86_64) 0 
minutes 53 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
  # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps 
/builddir/build/SPECS/rdma-core.spec

Just starting to dig into it, but if anyone has an "aha, that's XYZ", 
that might save me some time and effort. :)

(I get this with both rdma-core.spec and redhat/rdma-core.spec, btw)

-- 
Jarod Wilson
jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-03-22 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 15:44 Jarod Wilson [this message]
     [not found] ` <16cf8400-4920-c7ae-e0e5-c77a65a71460-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-22 16:22   ` Odd build failure in el7 mock Jason Gunthorpe
     [not found]     ` <20170322162245.GA18200-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-22 19:11       ` Leon Romanovsky
2017-03-22 20:43       ` Jarod Wilson
     [not found]         ` <1afb222d-5553-90d1-e18b-437e62012fff-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-22 21:06           ` Jason Gunthorpe

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=16cf8400-4920-c7ae-e0e5-c77a65a71460@redhat.com \
    --to=jarod-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).