From: Scott James Remnant <scott@ubuntu.com>
To: linux-ext4@vger.kernel.org
Cc: Theodore Tso <tytso@mit.edu>, util-linux-ng@vger.kernel.org
Subject: [PATCH] configure: Disable fsck wrapper on Linux by default
Date: Thu, 16 Jul 2009 19:50:15 +0100 [thread overview]
Message-ID: <E1MRWBp-0000yS-Dx@zelda.netsplit.com> (raw)
Since util-linux-ng now builds its fsck wrapper by default, e2fsprogs
should not do so on Linux (it already does not on Hurd).
Signed-off-by: Scott James Remnant <scott@ubuntu.com>
---
configure | 6 +++---
configure.in | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
index 5c272d8..9a29609 100755
--- a/configure
+++ b/configure
@@ -4855,15 +4855,15 @@ fi
else
case "$host_os" in
- gnu*)
+ gnu*|linux-gnu)
FSCK_PROG='' FSCK_MAN=''
{ $as_echo "$as_me:$LINENO: result: Not building fsck wrapper by default" >&5
$as_echo "Not building fsck wrapper by default" >&6; }
;;
*)
FSCK_PROG=fsck FSCK_MAN=fsck.8
- { $as_echo "$as_me:$LINENO: result: Building fsck wrapper by default" >&5
-$as_echo "Building fsck wrapper by default" >&6; }
+ { $as_echo "$as_me:$LINENO: result: Building fsck wrapper by default)" >&5
+$as_echo "Building fsck wrapper by default)" >&6; }
esac
fi
diff --git a/configure.in b/configure.in
index 25b9427..d9990b4 100644
--- a/configure.in
+++ b/configure.in
@@ -576,13 +576,13 @@ else
fi]
,
[case "$host_os" in
- gnu*)
+ gnu*|linux-gnu)
FSCK_PROG='' FSCK_MAN=''
AC_MSG_RESULT([Not building fsck wrapper by default])
;;
*)
FSCK_PROG=fsck FSCK_MAN=fsck.8
- AC_MSG_RESULT([Building fsck wrapper by default])
+ AC_MSG_RESULT([Building fsck wrapper by default)])
esac]
)
AC_SUBST(FSCK_PROG)
--
1.6.0.5
next reply other threads:[~2009-07-16 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 18:50 Scott James Remnant [this message]
[not found] ` <E1MRWBp-0000yS-Dx-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
2009-07-16 19:17 ` [PATCH] configure: Disable fsck wrapper on Linux by default Mike Frysinger
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=E1MRWBp-0000yS-Dx@zelda.netsplit.com \
--to=scott@ubuntu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=util-linux-ng@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