From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM tools RPM spec file for CVS builds
Date: Thu Nov 29 08:04:01 2001 [thread overview]
Message-ID: <20011129150534.C1283@sistina.com> (raw)
In-Reply-To: <3C04506F.6050603@larsshack.org>; from lars@larsshack.org on Tue, Nov 27, 2001 at 09:48:15PM -0500
Thanks Lars for providing this.
We'll check if we will integrate it into the LVM distro.
On Tue, Nov 27, 2001 at 09:48:15PM -0500, Lars Kellogg-Stedman wrote:
> In case someone else finds it useful...
>
> I've put an RPM spec file online at
> <http://larsshack.freeservers.com/lvm/> that will build the LVM user
> space tools using the current CVS tree.
>
> The spec file attempts to be clever and doesn't actually do a full
> checkout for each build -- only the first one. After that, it runs a
> cvs update.
>
> For folks experiencing the "help, <insert-command-name-here> segfaults"
> problem, you can pass rpm the "--with kgcc" flag on RedHat systems with
> the kgcc package installed, which will result in a non-segfaulting build.
>
> -- Lars
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-11-29 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:46 [linux-lvm] LVM tools RPM spec file for CVS builds Lars Kellogg-Stedman
2001-11-29 8:04 ` Heinz J . Mauelshagen [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=20011129150534.C1283@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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