linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Odd build failure in el7 mock
Date: Wed, 22 Mar 2017 15:06:16 -0600	[thread overview]
Message-ID: <20170322210616.GA21000@obsidianresearch.com> (raw)
In-Reply-To: <1afb222d-5553-90d1-e18b-437e62012fff-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, Mar 22, 2017 at 04:43:38PM -0400, Jarod Wilson wrote:

> The addition of 'relpath' in that commit means that python is now a
> BuildRequires of the rdma-core package. Once I added that, the package built
> in mock just fine. Will send a patch for it shortly.

Ah, yes..

I've also realized that execute_process does not abort cmake if it
fails, which is why this was hard for you to observe. That should be
fixed also..

Jason
--
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

      parent reply	other threads:[~2017-03-22 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 15:44 Odd build failure in el7 mock Jarod Wilson
     [not found] ` <16cf8400-4920-c7ae-e0e5-c77a65a71460-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-22 16:22   ` 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 [this message]

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=20170322210616.GA21000@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=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).