Re: libacm fails to build

[Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>]

On Thu, Mar 09, 2017 at 11:58:21PM +0000, Bart Van Assche wrote:
> 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
> > +++ 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 :-)

done

https://github.com/linux-rdma/rdma-core/pull/92

Thanks
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