From: jeffm@suse.com
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com, Jeff Mahoney <jeffm@suse.com>
Subject: [PATCH 0/3] btrfs-progs: build on SLE11
Date: Fri, 27 Apr 2018 14:56:34 -0400 [thread overview]
Message-ID: <20180427185637.16642-1-jeffm@suse.com> (raw)
From: Jeff Mahoney <jeffm@suse.com>
This patch set allows btrfs-progs to build without further patching
on a stock SLE11 SP4 install. The major issues were:
- new dependencies on e2fsprogs 1.42
- use of -std=gnu90, which gcc 4.3.4 doesn't support
- use of m4_chomp, introduced in autoconf 2.64.
This patch set is also posted as a GitHub pull request:
https://github.com/kdave/btrfs-progs/pull/125
-Jeff
---
Jeff Mahoney (3):
btrfs-progs: convert: fix support for e2fsprogs < 1.42
btrfs-progs: build: detect whether -std=gnu90 is supported
btrfs-progs: build: use m4_flatten instead of m4_chomp
Makefile | 1 -
Makefile.inc.in | 1 +
configure.ac | 10 +++---
convert/source-ext2.h | 12 +++++++-
m4/ax_check_compile_flag.m4 | 74 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 90 insertions(+), 8 deletions(-)
create mode 100644 m4/ax_check_compile_flag.m4
--
2.12.3
next reply other threads:[~2018-04-27 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 18:56 jeffm [this message]
2018-04-27 18:56 ` [PATCH 1/3] btrfs-progs: convert: fix support for e2fsprogs < 1.42 jeffm
2018-04-27 18:56 ` [PATCH 2/3] btrfs-progs: build: detect whether -std=gnu90 is supported jeffm
2018-04-27 18:56 ` [PATCH 3/3] btrfs-progs: build: use m4_flatten instead of m4_chomp jeffm
2018-04-27 19:18 ` Jeff Mahoney
2018-04-29 10:13 ` David Sterba
2018-04-29 13:19 ` Jeff Mahoney
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=20180427185637.16642-1-jeffm@suse.com \
--to=jeffm@suse.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox