From: "Alon Bar-Lev" <alon.barlev@gmail.com>
To: "Luciano Rocha" <luciano@eurotux.com>,
"Alon Bar-Lev" <alon.barlev@gmail.com>,
ldm@flatcap.org, ntfs-3g-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: ldminfo compilation
Date: Wed, 12 Dec 2007 16:57:39 +0200 [thread overview]
Message-ID: <9e0cf0bf0712120657p1a8fac7aoc5a82df1ff24daac@mail.gmail.com> (raw)
In-Reply-To: <20071212145241.GA25092@bit.office.eurotux.com>
On 12/12/07, Luciano Rocha <luciano@eurotux.com> wrote:
> Those are for the kernel module setting the partition tables. If you're
> only interested in the ldminfo utility:
> make -C ldmutil CPP='g++ -static'
>
> Substitute g++ for the C++ compiler you want to use.
Hi!
Thank you for your reply!
I don't really understand how to use the output of ldmutil in order to
do the dmsetup... All the instructions are for ldminfo...
And the C++ dependency does not work well with uclibc... I tried to
compile this using uclibc++, but the exception handling of uclibc++ is
broken for some strange reason... And I don't wish to introduce the
overhead of the C++ libraries to my system...
If ldmutil contain all the information, I will backport this to C and
be happy... :)
Can you please tell me how you use the output of this utility to merge
a spanned partition on two separate disks?
Best Regards,
Alon Bar-Lev.
next prev parent reply other threads:[~2007-12-12 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 14:39 Alon Bar-Lev
2007-12-12 14:52 ` Luciano Rocha
2007-12-12 14:57 ` Alon Bar-Lev [this message]
2007-12-12 15:29 ` Luciano Rocha
2007-12-12 16:40 ` Luciano Rocha
2007-12-12 22:59 ` Alon Bar-Lev
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=9e0cf0bf0712120657p1a8fac7aoc5a82df1ff24daac@mail.gmail.com \
--to=alon.barlev@gmail.com \
--cc=ldm@flatcap.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=luciano@eurotux.com \
--cc=ntfs-3g-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®