From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Nitin Kshirsagar <nshirsagar-FZ1t8LVTR2ZWk0Htik3J/w@public.gmane.org>
Cc: Kent Overstreet
<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Not able compile bcache-tools source code
Date: Tue, 22 Jan 2013 13:30:28 -0800 [thread overview]
Message-ID: <20130122213028.GE26407@google.com> (raw)
In-Reply-To: <C4B5704C6FEB5244B2A1BCC8CF83B86B0A6257C7C7-AQg6BlXVjylhNUoibfp7lHKnxlUjViKd@public.gmane.org>
On Tue, Jan 22, 2013 at 01:36:52PM +0800, Nitin Kshirsagar wrote:
> Hi,
>
> make install fails
> [root@annu bcache-tools]# make install
> install -m0755 make-bcache /usr/sbin/
> install -m0755 probe-bcache /sbin/
> install -m0644 61-bcache.rules /lib/udev/rules.d/
> install -m0755 initramfs/script /etc/initramfs-tools/scripts/init-premount/bcache
> install -m0755 initramfs/hook /etc/initramfs-tools/hooks/bcache
> install: cannot create regular file `/etc/initramfs-tools/hooks/bcache': No such file or directory
> make: *** [install] Error 1
That's just the initramfs script for bringing up bcache if your root fs
is a bcache device - if your distro isn't using initramfs, that's fine,
it's nothing to worry about.
I just pushed a patch to ignore errors on those two lines.
prev parent reply other threads:[~2013-01-22 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 13:19 Not able compile bcache-tools source code Nitin Kshirsagar
[not found] ` <C4B5704C6FEB5244B2A1BCC8CF83B86B0A6257C7C6-AQg6BlXVjylhNUoibfp7lHKnxlUjViKd@public.gmane.org>
2013-01-21 14:27 ` Kent Overstreet
[not found] ` <CAC7rs0uCU9B1SP4G4P1Di05hF=hZd1JJkipKd2UFrBBqEG2PBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-22 5:36 ` Nitin Kshirsagar
[not found] ` <C4B5704C6FEB5244B2A1BCC8CF83B86B0A6257C7C7-AQg6BlXVjylhNUoibfp7lHKnxlUjViKd@public.gmane.org>
2013-01-22 21:30 ` Kent Overstreet [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=20130122213028.GE26407@google.com \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nshirsagar-FZ1t8LVTR2ZWk0Htik3J/w@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.