All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zenon Panoussis <oracle@provocation.net>
To: ceph-devel@vger.kernel.org
Subject: dkms client module
Date: Thu, 14 Apr 2011 00:04:49 +0200	[thread overview]
Message-ID: <4DA61E01.9050505@provocation.net> (raw)


Hello all

I'm new to ceph and I'm having troubles with the client module.

I'm testing on SL6. RHEL6 and all its derivatives use kernel 2.6.32 and
will continue doing so for the next seven years. Therefore, the only
reasonable way to get ceph into RHEL6 is dkms. Luckily, that's already
supported.

I got ceph-client-standalone from git and fixed the specific 2.6.32
problems according to http://marc.info/?l=ceph-devel&m=129813044300561&w=2 .

Then I run into this:

 ./dkms/add-to-dkms-and-build

 Creating symlink /var/lib/dkms/ceph/2.6.37/source ->
                 /usr/src/ceph-2.6.37

 DKMS: add Completed.

 Kernel preparation unnecessary for this kernel.  Skipping...

 Building module:
 cleaning build area....
 make KERNELRELEASE=2.6.32-71.24.1.el6.x86_64 -C ceph/....(bad exit status: 2)

 Error! Bad return status for module build on kernel: 2.6.32-71.24.1.el6.x86_64 (x86_64)
 Consult the make.log in the build directory
 /var/lib/dkms/ceph/2.6.37/build/ for more information.
 0
 0

make.log says:

 DKMS make.log for ceph-2.6.37 for kernel 2.6.32-71.24.1.el6.x86_64 (x86_64)
 Wed Apr 13 23:47:41 CEST 2011
 make: Entering directory `/var/lib/dkms/ceph/2.6.37/build/ceph'
 make: *** No targets.  Stop.
 make: Leaving directory `/var/lib/dkms/ceph/2.6.37/build/ceph'

It seems to me there should be a Makefile in the root of ceph-client-standalone
that points make to the Makefiles of the subdirectories, but I'm an ignorant
wrt to make, so I'm not sure about anything.

Suggestions anyone how to get around this?

Z



             reply	other threads:[~2011-04-13 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 22:04 Zenon Panoussis [this message]
2011-04-14 16:44 ` dkms client module Yehuda Sadeh Weinraub

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=4DA61E01.9050505@provocation.net \
    --to=oracle@provocation.net \
    --cc=ceph-devel@vger.kernel.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.