All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nitin Kshirsagar <nshirsagar-FZ1t8LVTR2ZWk0Htik3J/w@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Not able compile bcache-tools source code
Date: Mon, 21 Jan 2013 06:27:09 -0800	[thread overview]
Message-ID: <CAC7rs0uCU9B1SP4G4P1Di05hF=hZd1JJkipKd2UFrBBqEG2PBw@mail.gmail.com> (raw)
In-Reply-To: <C4B5704C6FEB5244B2A1BCC8CF83B86B0A6257C7C6-AQg6BlXVjylhNUoibfp7lHKnxlUjViKd@public.gmane.org>

apt-get install libuuid-dev

On Mon, Jan 21, 2013 at 5:19 AM, Nitin Kshirsagar
<nshirsagar-FZ1t8LVTR2ZWk0Htik3J/w@public.gmane.org> wrote:
>
> Hi All,
>
> Source code URL: http://bcache.evilpiepirate.org/
> Compilation fails:
> [root@annu bcache-tools]# ls -1
> 61-bcache.rules
> bcache.c
> bcache.h
> bcache.o
> bcache-test.c
> COPYING
> initramfs
> make-bcache.8
> make-bcache.c
> Makefile
> probe-bcache.8
> probe-bcache.c
> README
> [root@annu bcache-tools]# make
> cc -O2 -Wall -g    make-bcache.c bcache.o  -luuid -o make-bcache
> make-bcache.c:20:23: error: uuid/uuid.h: No such file or directory
> make-bcache.c: In function ‘write_sb’:
> make-bcache.c:212: warning: implicit declaration of function ‘uuid_unparse’
> make-bcache.c:246: warning: implicit declaration of function ‘uuid_generate’
> make-bcache.c: In function ‘main’:
> make-bcache.c:280: warning: implicit declaration of function ‘uuid_parse’
> make: *** [make-bcache] Error 1
>
>
> --
> Thanks & Regards
>
> Nitin Kshirsagar
> Software Engr, QA
> Cell 997.566.3985
>
> STEC india private Limited, Pune | The SSD Company TM
> NASDAQ STEC • Web www.stec-inc.com
>
> PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED
>
> This electronic transmission, and any documents attached hereto, may contain confidential, proprietary and/or legally privileged information. The information is intended only for use by the recipient named above. If you received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of information received in error is strictly prohibited, and violators will be pursued legally.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-01-21 14:27 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 [this message]
     [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

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='CAC7rs0uCU9B1SP4G4P1Di05hF=hZd1JJkipKd2UFrBBqEG2PBw@mail.gmail.com' \
    --to=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.