From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Bart Van Assche <Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@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 15:49:04 -0700 [thread overview]
Message-ID: <20170309224904.GA5867@obsidianresearch.com> (raw)
In-Reply-To: <1489098918.2597.12.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
On Thu, Mar 09, 2017 at 10:35:30PM +0000, Bart Van Assche wrote:
> On Thu, 2017-03-09 at 10:10 -0700, Jason Gunthorpe wrote:
> > On Thu, Mar 09, 2017 at 11:25:27AM +0100, Philipp Thomas wrote:
> >
> > > I'm trying to build latest rdma-core but it fails in ibacm because a
> > > library is missing:
> >
> > The suse cmake rpm macros are broken, this is worked around in the
> > shipped rdma-core.spec:
> >
> > # Tumbleweed's cmake RPM macro adds -Wl,--no-undefined to the module flags
> > # which is totally inappropriate and breaks building 'ENABLE_EXPORTS' style
> > # module libraries (eg ibacmp).
> > %define CMAKE_FLAGS -DCMAKE_MODULE_LINKER_FLAGS=""
> >
> > Ideally you would consult internally to globally fix the rpm cmake
> > macro, otherwise you have to use the above hack..
>
> Something else is also broken, namely the SuSE section in rdma-core.spec. I
> just figured out that the following is needed to build an RPM on SuSE systems:
>
> diff --git a/rdma-core.spec b/rdma-core.spec
> index f7a440d7..aa486371 100644
> +++ b/rdma-core.spec
> @@ -28,7 +28,7 @@ BuildRequires: ninja,make
> %define __builder ninja
> # cmake_install,make_jobs is specified by opensuse
> %define cmake cmake
> -%define cmake_install DESTDIR=%{buildroot} ninja install
> +%define cmake_install DESTDIR=%{buildroot} make install
I'm not sure what tree you are looking at? The above '-' line never
appeared in mainline?
The opensuse rpm macros themselves are supposed to provide
cmake_install, so the spec file should not define it. Did they change
their macros again or something?
We provide it for the RH cases because they use a different cmake rpm
macro set. :(
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
next prev parent reply other threads:[~2017-03-09 22:49 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 [this message]
[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
[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=20170309224904.GA5867@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox