From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH] drbd-km.spec: Port to openSuSE
Date: Fri, 11 Sep 2015 14:44:33 +0200 [thread overview]
Message-ID: <20150911124433.GM3436@soda.linbit> (raw)
In-Reply-To: <55F1BECF.1000409@sandisk.com>
On Thu, Sep 10, 2015 at 10:33:03AM -0700, Bart Van Assche wrote:
> Currently building an RPM with the drbd-km.spec fails on openSuSE
> because of an incorrect build dependency (kernel-syms instead of
> kernel-default-devel). Fix the algorithm in the spec file for
> determining the kernel development RPM name. Note: if the kernel
> development headers have not been installed as an RPM the
> %{kernel_devel_rpm} variable will be empty.
>
> This patch has been tested on openSuSE 13.2, CentOS 7.1 and SLES11 SP3.
You are not supposed to build a "drbd-km" from "drbd-km.spec",
you are supposed to build a kmod-drbd (resp. drbd-kmp) from "drbd-kernel.spec",
using the kernel module build "magic" of the respective ditribution.
(not "make km-rpm", but "make kmp-rpm")
But thanks ;-)
Lars
prev parent reply other threads:[~2015-09-11 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 17:33 [Drbd-dev] [PATCH] drbd-km.spec: Port to openSuSE Bart Van Assche
2015-09-11 12:44 ` Lars Ellenberg [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=20150911124433.GM3436@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/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