[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using result of AC_PROG_SED as sed program in config.status
From: |
Albert Chin |
Subject: |
Re: Using result of AC_PROG_SED as sed program in config.status |
Date: |
Fri, 4 Feb 2005 03:16:39 -0600 |
User-agent: |
Mutt/1.5.6i |
On Fri, Feb 04, 2005 at 12:31:13AM -0800, Paul Eggert wrote:
> Part of my reluctance is that I have my doubts about these "nicer"
> seds that lack line limits. On Solaris 2.6 and 7, for example, my
> experience was that the "nicer" sed wasn't tested or maintained as
> much.
So why don't we ignore /usr/xpg4/bin/sed and choose either 'sed' from
$PATH or 'gsed'? Changing AC_PROG_SED for this is trivial.
--- lib/autoconf/programs.m4 2005-02-03 16:02:29.000000000 -0600
+++ lib/autoconf/a 2005-02-04 03:16:15.000000000 -0600
@@ -732,7 +732,7 @@
[AC_CACHE_CHECK([for a sed that does not truncate output], ac_cv_path_SED,
[_AC_PATH_PROG_FEATURE_CHECK(SED, [sed gsed],
[_AC_FEATURE_CHECK_LENGTH([ac_path_SED], [ac_cv_path_SED],
- ["$ac_path_SED" -e 's/a$//'])], [$PATH:/usr/xpg4/bin])])
+ ["$ac_path_SED" -e 's/a$//'])], [$PATH])])
SED="$ac_cv_path_SED"
AC_SUBST([SED])
])# AC_PROG_SED
--
albert chin (address@hidden)