From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: markw@mohawksoft.com
Subject: Re: [linux-lvm] Building thin-provisioning tools > 1.4 on RHEL 6.4
Date: Thu, 11 Jul 2013 09:58:15 +0200 [thread overview]
Message-ID: <51DE6597.20705@gmail.com> (raw)
In-Reply-To: <13d9860ff7a6b54efeecea353ecd6b98.squirrel@mail.mohawksoft.com>
Dne 11.7.2013 02:12, markw@mohawksoft.com napsal(a):
> This is half request half rant.
>
> Is there a way to compile the latest thin-provisioning tools on RHEL 6.4?
> The introduction of C++11 and Boost currently makes this impossible with
> standard development tool chain in the release.
>
> Are there any plans to support the RHEL tool chain? I dread building a new
> gcc and all that involves.
>
For now I'd suggest to stay with tagged version v0.1.4.
Zdenek
prev parent reply other threads:[~2013-07-11 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 0:12 [linux-lvm] Building thin-provisioning tools > 1.4 on RHEL 6.4 markw
2013-07-11 7:58 ` Zdenek Kabelac [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=51DE6597.20705@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=markw@mohawksoft.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;
as well as URLs for NNTP newsgroup(s).