All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: "jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org"
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: "pth-l3A5Bk7waGM@public.gmane.org"
	<pth-l3A5Bk7waGM@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: libacm fails to build
Date: Thu, 9 Mar 2017 23:58:21 +0000	[thread overview]
Message-ID: <1489103888.2597.21.camel@sandisk.com> (raw)
In-Reply-To: <20170309235406.GA16385-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>

On Thu, 2017-03-09 at 16:54 -0700, Jason Gunthorpe wrote:
> Yes, I think so, like this?
> 
> diff --git a/rdma-core.spec b/rdma-core.spec
> index 6519bc370a230a..df65745ff9c468 100644
> --- a/rdma-core.spec
> +++ b/rdma-core.spec
> @@ -26,7 +26,9 @@ BuildRequires: valgrind-devel
>  # SuSE releases have it, and sometime around cmake 3.3.2-1.2 the macros learned to use it.
>  BuildRequires: ninja,make
>  %define __builder ninja
> -# cmake_install,make_jobs is specified by opensuse
> +# cmake_install is specified by opensuse. It also specifies make_jobs, but it
> +# doesn't work with __builder as other rpm macro packages define it too.
> +%define make_jobs ninja-build -v %{?_smp_mflags}
>  
>  # Tumbleweed's cmake RPM macro adds -Wl,--no-undefined to the module flags
>  # which is totally inappropriate and breaks building 'ENABLE_EXPORTS' style

If ninja-build is changed into ninja or %{__builder} then I agree :-)

Thanks,

Bart.--
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-09 23:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 10:25 libacm fails to build Philipp Thomas
     [not found] ` <20170309102527.3ni4pkuendwzqzrm-TXhXIaCUHZEYitT5tn2FcQ@public.gmane.org>
2017-03-09 17:10   ` Jason Gunthorpe
     [not found]     ` <20170309171014.GC12694-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-09 22:35       ` Bart Van Assche
     [not found]         ` <1489098918.2597.12.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-03-09 22:49           ` Jason Gunthorpe
     [not found]             ` <20170309224904.GA5867-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-09 22:53               ` Bart Van Assche
     [not found]                 ` <1489099998.2597.16.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-03-09 23:04                   ` Jason Gunthorpe
     [not found]                     ` <20170309230453.GA7844-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-09 23:12                       ` Bart Van Assche
     [not found]                         ` <1489101151.2597.18.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-03-09 23:23                           ` Jason Gunthorpe
     [not found]                             ` <20170309232352.GA12387-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-09 23:47                               ` Bart Van Assche
     [not found]                                 ` <1489103252.2597.20.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-03-09 23:54                                   ` Jason Gunthorpe
     [not found]                                     ` <20170309235406.GA16385-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-09 23:58                                       ` Bart Van Assche [this message]
     [not found]                                         ` <1489103888.2597.21.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-03-10 18:43                                           ` 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=1489103888.2597.21.camel@sandisk.com \
    --to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pth-l3A5Bk7waGM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.