From: Chris Mason <chris.mason@fusionio.com>
To: Christian Hesse <list@eworm.de>
Cc: Chris Mason <clmason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: fix btrfs-progs build
Date: Mon, 8 Oct 2012 10:33:51 -0400 [thread overview]
Message-ID: <20121008143351.GD4132@shiny> (raw)
In-Reply-To: <20121008163031.4656b6ff@leda>
On Mon, Oct 08, 2012 at 08:30:31AM -0600, Christian Hesse wrote:
> Chris Mason <chris.mason@fusionio.com> on Mon, 2012/10/08 10:29:
> > On Mon, Oct 08, 2012 at 08:17:13AM -0600, Christian Hesse wrote:
> > > Hello everybody,
> > >
> > > man pages for btrfs-progs are compressed by gzip by default. In Makefile
> > > the variable GZIP is use, this evaluates to 'gzip gzip' on my system.
> > > From man gzip:
> > >
> > > > The environment variable GZIP can hold a set of default options for
> > > > gzip. These options are interpreted first and can be overwritten by
> > > > explicit command line parameters.
> > >
> > > So using any other variable name fixes this. Patch is attached.
> >
> > Ok, which system is this? Just curious, I'll pull in the patch.
>
> This is Arch Linux with gzip 1.5-1.
Strange, I'm running running arch linux with gzip 1.5-1 and it builds.
I wonder if something else is expanding it. I'll take the patch
regardless, there's no reason to add build problems when we don't need
to.
-chris
next prev parent reply other threads:[~2012-10-08 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 14:17 fix btrfs-progs build Christian Hesse
2012-10-08 14:29 ` Chris Mason
2012-10-08 14:30 ` Christian Hesse
2012-10-08 14:33 ` Chris Mason [this message]
2012-10-08 14:45 ` Christian Hesse
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=20121008143351.GD4132@shiny \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@eworm.de \
/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.