Re: solaris link line length problem == buggy sed

[Robert Boehne]

Typos, sorry!  Here's a proper version.

Rob

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden

? deplib-test
? missing
? confdefs.h
? sedtest
? install-sh
? INSTALL
? depcomp
? mkinstalldirs
? COPYING
? sed-check.patch
? libltdl/config-h.in
Index: ChangeLog
===================================================================
RCS file: /cvsroot/libtool/libtool/ChangeLog,v
retrieving revision 1.979
diff -u -r1.979 ChangeLog
--- ChangeLog   2001/07/17 20:17:38     1.979
+++ ChangeLog   2001/07/18 22:53:37
@@ -1,3 +1,10 @@
+2001-07-18  Robert Boehne  <address@hidden>
+
+       * libtool.m4 (AC_LIBTOOL_SED_TRUNCATE): New macro that
+       determines whether or not the sed program being used by
+       libtool truncates its output up to 10010 characters on
+       a single line.
+ 
 2001-07-16  Robert Boehne  <address@hidden>, Tim Mooney  <address@hidden>
 
        * ltdl.m4 (AC_LTDL_SYS_DLOPEN_DEPLIBS): add cases and comments for
Index: libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/libtool.m4,v
retrieving revision 1.195
diff -u -r1.195 libtool.m4
--- libtool.m4  2001/07/16 19:11:34     1.195
+++ libtool.m4  2001/07/18 22:53:38
@@ -95,6 +95,7 @@
 AC_REQUIRE([AC_EXEEXT])dnl
 dnl
 
+AC_LIBTOOL_SED_TRUNCATE
 AC_LIBTOOL_SYS_MAX_CMD_LEN
 AC_LIBTOOL_SYS_GLOBAL_SYMBOL_PIPE
 AC_LIBTOOL_OBJDIR
@@ -535,6 +536,48 @@
     ifelse([$5], , :, [$5])
 fi
 ])# AC_LIBTOOL_LINKER_OPTION
+
+
+# AC_LIBTOOL_SED_TRUNCATE
+# --------------------------
+AC_DEFUN([AC_LIBTOOL_SED_TRUNCATE],
+[# Check the sed program to see if it truncates its output
+AC_MSG_CHECKING([if sed truncates output lines])
+AC_CACHE_VAL([lt_cv_buggy_sed], [dnl
+if sed -V 2>&1 | egrep 'GNU' > /dev/null; then
+  # We are using GNU sed, which doesn't truncate.
+  lt_cv_buggy_sed="no"
+else
+  cat > conftest.$ac_ext <<EOF
+[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]
+EOF
+  i=0
+  # The number 415 gives us 10,010 characters, probably
+  # enough to catch yet unknown seds that have this problem.
+  while test $i != 415
+  do
+    i=`expr $i + 1`
+    echo | awk '{ printf "XXXXXXXXXXXXXXXXXXXXXXXX"; }' >> conftest.$ac_ext
+  done
+  sed 's/Y/Z/' conftest.$ac_ext > conftest.out
+  lt_cv_buggy_sed="yes"
+  ( cmp conftest.$ac_ext conftest.out 2>&1 && lt_cv_buggy_sed="no" ) >/dev/null
+  rm -f conftest.$ac_ext conftest.out
+fi
+])
+AC_MSG_RESULT($lt_cv_buggy_sed)
+if test $lt_cv_buggy_sed != "no" ; then
+       cat <<EOF 1>&2
+
+*** Warning: the sed program libtool is configured to use, sed,
+*** truncates its output.  The result is that libtool may be unable
+*** to create large libraries without run-time errors.
+*** Configure libtool to use GNU sed, or an alternative sed program
+*** that does not truncate its output.
+
+EOF
+fi
+])# AC_LIBTOOL_SED_TRUNCATE
 
 
 # AC_LIBTOOL_SYS_MAX_CMD_LEN